Discovery Tests

Use discovery tests to explore an app and find issues, especially in new features or areas without a regression suite. The agent chooses actions as it explores and reports bugs it encounters.

Create a Discovery test in the Repository, select an agent, and set a minimum and maximum time budget for the whole test.

Set an Exploration Scope

The editor has one optional scope field:

• Leave it empty for broad exploration of the app.
• Enter a scope to focus on a feature, flow, or recent fix.

For example:

Explore the shop. Try purchasing items, switching categories, and
returning to the main menu. Check that displayed prices match the
amounts charged and purchased items appear in the inventory.

Use show hints for guidance such as how to access the shop or recover from a popup. Attach knowledge files, such as a feature specification, to give the agent a reference for intended behavior.

Review and Follow Up

Review reported issues in Bugs and inspect the recording and evidence in Run Details.

For broader coverage, run several focused explorations with different scopes. Turn scenarios you want to check on every build into verification tests with explicit expected results.