Verification Tests

Use verification tests for repeatable smoke and regression checks. A test is an ordered route through the app, with individual expected results to verify along the way.

Create a Verification test in the Repository. Set a maximum time budget for the whole test, select the agent, and add steps.

Writing Steps and Checks

Start by listing the checks you need, then group checks visible on the same screen or during the same operation into a step. Order the steps into a practical route through the app.

Each step contains:

Field	What to write
Goal/instructions	The actions that reach the state being checked, with a clear endpoint.
Expected results	Separate, observable yes/no checks. Use one row per fact that can pass or fail independently.
Hints	Optional navigation, recovery, or interaction guidance, available under show hints.

Click add result or press Enter while editing a result to add another check. Shift+Enter adds a line break within the same check.

Name the visible element and its expected state. For values that vary between runs, describe the relationship: “The balance increases by the displayed reward amount.” Give hints an action, such as “If a news popup covers the menu, close it.”

Setup and Reuse

Begin with steps that establish the required account, data, and screen. Account for the starting state of your deployment, including saved state on private devices.

Group related steps into named collections. Use Shared Steps for sequences reused across verification tests, such as guest login. End each sequence in a known state for the next step.

Example Step

For a document upload in a web app:

Goal/instructions: Open Documents, upload the prepared sample.pdf, and name it Release notes.

Expected results (one row each):

A document named Release notes appears in the Documents list.
That document’s filename is sample.pdf.

Hints:

If Upload stays enabled and no progress appears after clicking, locate the button again in the current view and retry. The file preview can change the dialog’s layout.
Wait for the upload-complete message, then search for Release notes and let the list finish loading before checking the document.

These hints guide the agent back to the same checks. See Recovery Hints for more examples.

Review Results

In Run Details, inspect each check’s outcome and evidence. Checks can be passed, failed, skipped, or blocked. The agent can continue with reachable checks after a failure; a blocking issue can prevent later checks from being exercised.

Use Best Practices to refine unstable tests. For AI-assisted authoring and TestRail imports, see the verification test authoring skill .