Skip to main content
Manage the results directory produced by momentic run. Use upload after running with --upload-results disabled, merge to combine sharded runs, view to inspect runs locally without uploading, and check to gate CI on truly clean results.

upload

Upload local test results to the Momentic dashboard.

Arguments

string
Folder containing results from momentic run or momentic results merge. Defaults to test-results, which matches the default --output-dir of momentic run, so you can usually omit this argument.

merge

Merge results from multiple sharded runs into a single folder before uploading.

Arguments

string
required
Parent folder of the results to merge. For example, if shards wrote into test-results/shard-1 and test-results/shard-2, pass test-results.

Options

string
Directory to write the merged results to. The folder is overwritten if it exists.
boolean
Include run groups that produced no runs, such as shards where AI test selection chose zero tests. Their metadata, including the selection plans, is merged instead of skipped, so the uploaded run group can explain why nothing ran. A results path that is missing or contains no run groups becomes a graceful no-op instead of an error. Recommended whenever AI selection is enabled; upload and check accept the same flag so the whole chain can run unconditionally in CI.

view

Launch the local run viewer to inspect results without uploading.

Arguments

string
required
Path to a folder containing a runs/ subfolder. Defaults to test-results.
string
Run ID to open, matching a zip file in the runs/ subfolder. For example, for runs/eed92602-7355-43dc-8d79-1c43029bec26.zip, pass eed92602-7355-43dc-8d79-1c43029bec26. When omitted, the viewer opens to the run group table.

Options

number
Port for the local run viewer server. Defaults to 58889.

check

Exit non-zero if any non-quarantined run in a results archive did not pass cleanly. Use it as a CI gate after merge to require truly green results.
A run is considered not clean (and the command exits 1) when it is not quarantined and any of the following is true:
  • its final status is FAILED or CANCELLED,
  • it only passed after an in-run failure recovery, or
  • it carries a failure classification (any category, including ones routed to heal/warn).
Quarantined runs are always ignored. The command exits 0 only when every non-quarantined run passed outright with no recovery and no classification. Pass --allow-recovered to treat runs that passed via in-run failure recovery as clean: they no longer fail the check, while FAILED/CANCELLED runs and failure classifications still exit 1.

Arguments

string
required
Path to a folder containing a runs/ subfolder, typically the --output-dir of a preceding momentic results merge.

Options

boolean
Treat runs that passed via in-run failure recovery as clean (exit 0).
boolean
Suppress progress output and print the check report as JSON. The report includes per-run detail for each not-clean run (uncleanRuns) and a summary with descriptive per-category counts: total, clean, quarantined, failed, cancelled, recovered, and classified. These counts overlap (a run can be both recovered and classified), so they do not sum to total.

Examples

Upload the default results folder:
Merge sharded results before uploading:
View a specific run locally on a custom port:
Gate CI on clean results after merging shards: