Setup with coding agent
Paste this prompt into your coding agent from your project directory. It checks setup, runs the wizard when needed, and asks for your app build.Setup prompt
Prerequisites
Use Node.js 22.12 or later in the 22.x line, or 24 or later, a Momentic account, and a project with apackage.json. Run npm init -y if needed; commit it with
the lockfile.
Install Android SDK platform-tools
and set ANDROID_HOME or ANDROID_SDK_ROOT to the SDK directory. Remote
emulators need adb too, but no local Java, Android Studio, or APK for the
wizard’s sample. Local emulators need JDK 24+ and Android Studio.
Check the SDK before continuing:
1
Install with the wizard
Run from your project root and complete browser sign-in:Select Android. The wizard installs
momentic-mobile, writes
momentic.config.yaml and a sample under android/, runs it on a
remote emulator, and offers coding agent setup. A passing sample
verifies installation, not your app.Already configured? Skip the wizard. See the
CLI reference for manual setup.2
Upload your app
Build an APK with the
Android build instructions.
Apps with WebView content must enable
WebView debugging.
Upload it to a channel and an unused tag:For a local device instead, configure your
emulator.Keep the channel and tag for the next step: they identify the APK
your test installs. For later builds, choose a new tag. See
asset uploads
for versioning and upload options.
3
Write and run a test
Open the local editor:Create a test using channel
dev and tag 1.0.0. Add an action
such as tapping Sign in, then assert that the sign-in form is visible.
Choose an outcome that matches your app. Save the .test.yaml file
and run it from the editor, then from the CLI:4
Review the result
Open the printed dashboard link and check the assertion screenshot.
Confirm the run passed and the device shows the expected state.
If it fails, inspect the selected build, sign-in state, and assertion,
then edit and rerun.Keep the YAML file in version control with your app. The local editor
writes the test; the cloud dashboard shows uploaded run results.
You don’t need a browser-based mobile editor to run the saved file
again from your terminal or CI.