--upload-results to send them to the
dashboard after the run completes. Requires tests to exist locally as YAML
files.
Arguments
Tests to run, given as test file paths, directories, or test-name substrings.
Defaults to every test in the current project.
Common flags
Path to the Momentic configuration file. When omitted, Momentic searches the
current directory and its parents for
momentic.config.yaml or a workspace
configuration. Use this flag to select a project when discovery finds more
than one.Name to associate with this run, used in the dashboard and as the base
filename for generated reports.
Number of tests to run in parallel. Uses the project’s
parallel setting,
then 1. Pass AUTO to run every test in the current shard concurrently.Remote runs give each test an independent emulator session, so parallelism is
safe and any org quota is enforced server-side. Local Android runs require a
distinct AVD per parallel test; running multiple tests against the same
--local-avd-id conflicts. Use --parallel 1 for local iOS runs to avoid
concurrent sessions sharing a device-driver manifest.Environment
Environment to run tests in. Must exist in the project configuration and takes
precedence over the default environment configured on the test.
Region used for remote emulator sessions. Overrides any region configured at
the project or environment level. Pass
closest to autoselect the nearest
region.Override the default release channel for app build selection (e.g.
staging,
dev). When omitted, falls back to the test’s default channel; if the test
has none, no app build is installed during device initialization.Override the version tag within the selected channel. Accepts an exact tag,
the reserved
latest, or a floating alias (e.g. nightly). When omitted,
uses the test’s default tag; if the test has no default, the latest uploaded
build for the test’s platform in the channel applies.Filtering
Only include tests whose file path matches any of the provided regex patterns.
The pattern only needs to match part of the path.
Video
Record videos of mobile test runs. Accepts
true, false, or on-fail.
Defaults to on-fail (videos are recorded but kept only for failing tests).Quarantine
Skip quarantined tests entirely. By default, quarantined tests still run but
their statuses do not affect pipeline status or the process exit code.
Run all selected tests and apply quarantined tests’ statuses to the pipeline
status and exit code. Use it to verify fixes before unquarantining.
Caching
Always save updated step caches after successful runs, even on the main and
other protected Git branches. See cache saving
eligibility.
Run without using existing step caches. Saving still follows the normal branch
rules; add
--save-cache to save on protected branches. Use it to refresh
caches after a config change.Visual diff
Update locally stored golden files for
visualDiff steps. Without this
flag a visualDiff step fails when the screenshot differs from its golden;
the run creates missing goldens on first run regardless of this flag.Sharding
Output
Directory to store run artifacts (screenshots, logs, results). Defaults to the
project’s
outputDir or ./test-results. The directory is cleared at the
start of a run.Upload test results to the Momentic dashboard after the run. Equivalent to
running
momentic-mobile results upload <outputDir> once the run finishes.Output reporter. Pass multiple times to combine reporters
(e.g.
--reporter=list --reporter=junit).Live reporters render progress to the terminal as the run unfolds:list: per-test rows. Default. On a TTY the running rows redraw in place with their current step; on non-TTY each test commits a single row when it finishes.steps: append-only lines logging each step as it starts and finishes, with per-step durations, sections (setup/main/teardown), and nesting via indentation (modules, AI actions, loops). Use it for CI logs, which do not render thelistreporter’s in-place redraws.
--reporter-dir. Mobile runs support:jsonjunitallureallure-jsonbuildkite-json
Directory where reporter output is saved. Defaults to
./reports. Filenames
derive from --name (or the project name).Local devices
Force tests to use a specific local Android Virtual Device (AVD). Overrides
all configuration at the test and environment level.
Force tests to use a specific local iOS simulator device type. Accepts any
option Xcode supports when creating a new simulator (e.g.
"iPhone 17").CI
Maximum total run time, in minutes. When reached, running tests stop and the
CLI prints current results.