Results and reporting

Momentic produces results in two places:

The dashboard at app.momentic.ai: uploaded run data with videos, traces, auto-heal history, and quarantine state.
Local reports: JUnit XML, Allure, Playwright JSON, or Buildkite JSON, for feeding into other CI tooling.

Uploading to the dashboard

Pass the upload flag on any run invocation:

npx momentic run --upload-results

npx momentic-mobile run --upload-results

Uploaded runs appear in the Runs view in the dashboard. MOMENTIC_API_KEY must be set.

Group independent invocations

If your orchestrator starts separate CLI processes for one batch, generate one UUID and pass it to every invocation:

BATCH_UUID=$(node -e 'process.stdout.write(crypto.randomUUID())')
momentic run path/to/checkout.test.yaml \
  --run-group-id "$BATCH_UUID" \
  --upload-results
momentic run path/to/refunds.test.yaml \
  --run-group-id "$BATCH_UUID" \
  --upload-results

Every invocation uploads independently, including deferred momentic results upload calls. After Momentic indexes the uploads, their physical runs appear in the same run group. This is an eventually consistent group, not a finalized batch. Use the same UUID and consistent suite, project, and Git metadata for every invocation. After your orchestrator submits every upload, it can start triage immediately with the shared UUID; triage waits for normal upload indexing and does not wait for the group projection to settle. Upload each result directory separately; do not merge the archives first.

Every uploaded run surfaces with:

Status: pass, fail, flaky, quarantined, cancelled
Duration and cost: time the run took plus AI token usage
Environment and branch: which env and Git branch the run targeted
Trigger: CLI, API, scheduled, or manual

Filtering

Filter runs by test name or label, environment or branch, status, time range, or trigger type. Saved filters live in the left sidebar.

Drilling into a run

Each run page shows every step with its status, duration, and artifacts. Click a step to view its video replay, trace (DOM, network, console), screenshots, auto-heal traces when healing fired, and AI reasoning. For steps that used element location, the detail pane also includes a Cache section showing whether the step used cache, missed cache, busted cache before use, or had no cache, along with the reason when available. In the dashboard, the Cache section of a cached step also lets you inspect and invalidate the entry without leaving the run. This works for web and mobile runs, however they were triggered:

Expand Cached value to read the stored locator or assertion result.
Choose Clear step cache to drop the entry, so the next run resolves the step fresh with AI. A run on a feature branch clears the entry for that branch only; a run on your main branch clears it everywhere.

The result tree keeps noisy step structures compact:

Conditional rows read as If ... and show the evaluated outcome inline as = true or = false.
Retried steps collapse to one final row with a retry count; expand it to see each Attempt N.
While loops expand into Iteration N groups so each pass through the body is inspectable.

You can also inspect the same run UI locally against a folder of run results using momentic results view (or momentic-mobile results view for mobile). Each run has a shareable URL. Team members with workspace access can open it directly.

Generating local reports

Pass --reporter to run to emit a standardized report file into the reporterDir (defaults to ./reports):

npx momentic run --reporter junit

npx momentic-mobile run --reporter junit

Supported formats:

Format	Web	Mobile	Notes
`json`	Yes	Yes	Momentic JSON report with structured run results and classifications.
`junit`	Yes	Yes	JUnit XML. Drops into any CI system that surfaces JUnit.
`allure`	Yes	Yes	Allure result directory.
`allure-json`	Yes	Yes	Allure JSON results (one file per test).
`playwright-json`	Yes	No	Playwright-style JSON report.
`buildkite-json`	Yes	Yes	Buildkite Test Analytics JSON format.
`newrelic`	Yes	No	Pushes custom events to New Relic instead of writing a file.

See momentic run and momentic-mobile run for the full CLI flag reference.

Live run progress

While a run is in flight, momentic run and momentic-mobile run write a progress.json file to the top of the --output-dir (defaults to ./test-results). It is updated as steps complete, so you can poll it to track long runs (for example, to report that a test has finished “53 of 70 steps”) or forward it to your own reporting pipeline. The file holds an aggregate roll-up plus one entry per test run:

{
  "schemaVersion": "1.0.0",
  "runGroupId": "01J...",
  "status": "RUNNING",
  "totalRuns": 2,
  "completedRuns": 1,
  "completedSteps": 58,
  "totalSteps": 124,
  "startedAt": "2026-06-13T03:11:00.000Z",
  "updatedAt": "2026-06-13T03:12:04.000Z",
  "runs": [
    {
      "runId": "01J...",
      "testId": "abc123",
      "testName": "checkout/happy-path",
      "directory": "checkout",
      "status": "PASSED",
      "completedSteps": 70,
      "totalSteps": 70,
      "startedAt": "2026-06-13T03:11:00.000Z",
      "updatedAt": "2026-06-13T03:11:48.000Z"
    },
    {
      "runId": "01J...",
      "testName": "checkout/coupon",
      "status": "RUNNING",
      "completedSteps": 53,
      "totalSteps": 70,
      "startedAt": "2026-06-13T03:11:48.000Z",
      "updatedAt": "2026-06-13T03:12:04.000Z"
    }
  ]
}

Notes on the counts:

completedSteps / totalSteps count top-level steps. An AI action and its substeps count as one step; a module or section counts as one plus its nested steps; a conditional counts as one assertion plus its largest branch (only one branch runs); a while loop counts as one step regardless of iterations. Steps that failure recovery adds while repairing a failed step are not counted.
The file is written atomically and updated on a short throttle, so a reader always sees a complete, valid JSON document.
When tests are sharded across multiple machines, each shard has its own --output-dir and therefore its own progress.json. When tests run across parallel workers on a single machine, the parent process writes one merged progress.json covering all workers.

CI integration

Every CI/CD template uploads results by default. See your CI provider’s page for the ready-to-paste config.

Artifacts

Failed runs include:

Video: enable via recordVideo in momentic.config.yaml
Trace: always captured on failure
Screenshots: captured at each step
Auto-heal traces: shown in the run viewer when auto-heal fires

All artifacts are visible in the dashboard; local artifacts live under reporterDir.

Viewing runs outside the dashboard

The result viewer behind momentic results view also ships as a static bundle you can host yourself. Use it to serve run results from your own infrastructure. See Self-host the result viewer.

Get started

Author

Run

Learn

Platforms

Integrations

Advanced

Migrations

Account

Results and reporting

Uploading to the dashboard

Group independent invocations

Filtering

Drilling into a run

Generating local reports

Live run progress

CI integration

Artifacts

Viewing runs outside the dashboard

​Uploading to the dashboard

​Group independent invocations

​Filtering

​Drilling into a run

​Sharing

​Generating local reports

​Live run progress

​CI integration

​Artifacts

​Viewing runs outside the dashboard

Uploading to the dashboard

Group independent invocations

Filtering

Drilling into a run

Sharing

Generating local reports

Live run progress

CI integration

Artifacts

Viewing runs outside the dashboard