Give the agent an expected user outcome, then verify that outcome in a real browser. Code generation and browser verification are separate steps.
Ask for the customer outcome, such as a saved setting remaining visible after navigation. Avoid an assertion that merely checks the generated component exists. A browser pass should establish the requirement you intended, not the implementation detail the agent happened to choose.
The optional CLI exposes MCP tools to list, read, save, draft, verify and run repository tests. Saving changed YAML invalidates earlier verification. The browser run produces the result; a proposed test is not a passing test until that exact revision executes successfully.
Yes, through the optional CLI MCP server in a compatible client. Configure the project and authenticate first.
No. Local runs use Zerocheck’s AI service and upload results and artifacts to the web app.
Describe a customer flow or paste your release checklist, review the browser result, and save the tests you want to rerun.
Get a demo