Define what matters. Let Momentic verify it.
Write steps and assertions in plain-English YAML.
Review and version the tests in your repository.
01 / author
Write tests in plain English
Describe a user flow and its expected result in plain English. Keep the steps and assertions in YAML files your team and coding agent can review.
standard-user-purchases.test.yaml - momentic
storefront
tests
modules
1
fileType: momentic/test/v22
id: standard-user-checkout3
url: https://shop.momentic.ai4
description: End-to-end checkout flow5
steps:6
- module: ./log-in-username-password.module.yaml7
- act: add the momentic backpack to the cart and go to checkout8
- module: ./fill-out-personal-info.module.yaml9
- assert: the item total matches the amount listed for each item10
- click: Finish buttonmomentic run
02 / run
Run locally and in CI
Use the CLI to check the app you're changing. Run the same tests in CI before the next merge or deploy.
03 / triage
Find the root cause
See which step failed and inspect its screenshots and traces. AI triage investigates the cause and proposes a test repair for you to review.
momentic ai classify --interactive
Ask a follow-up about this runctrl-c to exit
github.com
tests/standard-user-purchases.test.yaml+1−1
@@ checkout flow · steps 3-5 @@
- module: ./fill-out-personal-info.module.yaml - assert: the item total matches the amount listed for each item-
- click: Finish button+
- click: Place Order buttonmomentic ai heal
04 / heal
Auto-heal as your product evolves
Momentic finds controls again when the UI changes. Permanent healing proposes test-file edits for review. Apply the diff and rerun to check the result.