Skip to main content
Agentic testing uses AI agents across the test lifecycle: an agent drives a flow from a natural-language goal, repairs tests when the UI changes, and proposes new tests as the product changes. Use it when maintaining a hand-written test suite in sync with a changing product takes more effort than it is worth. An agentic step takes a goal and a post-condition. The agent drives the flow and the assertion verifies the outcome:
checkout.test.yaml

​
When to use it

  • Your UI changes often enough that hard-coded selectors break constantly.
  • A flow’s exact steps are not predictable ahead of time: they vary by feature flag, A/B test, or user state.
  • You want coverage to stay current as the product changes. Agentic steps can cover journeys without hand-writing a test for every change.

​
Step-based vs agentic

This is the main decision, and it is per step, not per test suite. Most tests should stay step-based; reach for an agentic step only where a fixed script does not fit. Keep critical paths step-based so they are fast and you can assert exact outcomes. Use agentic steps for the parts that genuinely vary, and wrap each one in an assertion so the outcome is still checked. See agentic testing for the full trade-offs.

​
Where agents help across the lifecycle

  • Authoring: write a goal as an AI action step, or connect your coding agent to the MCP server and author tests for the journeys a change touches. Give agents reusable context with a knowledge base so they use your terminology and flows.
  • Repair: auto-heal fixes a test mid-run when the UI changed, so a moved or renamed element does not fail a test that still works.
  • Maintaining coverage: use the momentic-spec skill as you implement a change, so the tests for a new journey land with the pull request. See PR testing.

​
Keep it trustworthy

Agentic steps are flexible but non-deterministic. Constrain them so a run stays trustworthy:
  • Wrap each agentic step in an explicit assertion so a run verifies the outcome, not just that the agent finished.
  • Keep goals short and specific. “Sign up a new user with a fresh email” works better than “test the onboarding flow.”
  • Pass anything the agent cannot infer (invite codes, IDs) via variables.

​
Get started

1

Write your first agentic step

Add an AI action step with a goal and a post-condition. See agentic testing.
2

Let auto-heal maintain it

Auto-heal repairs the test when the UI changes, so routine edits do not break it.
3

Fill gaps from your coding agent

Use the momentic-spec skill to author tests for the journeys a change touches.

Agentic testing

AI action steps and when to use a goal instead of fixed steps.

MCP server

Author and maintain tests from your coding agent.

Auto-healing

Repair tests when the UI changes.

Knowledge base

Give agents reusable context about your product.