Test Detail Page

​

Overview

Every project has its own detail page, the home base for its coverage map, test cases, runs, and settings. Open a project from All Projects and you land on its Test Cases (or, while the project is still being set up, on the stage it has reached or its Onboarding Checklist). Everything else is one click away in the left nav. The header carries Share (invite someone to the workspace so they can open this project; see Sharing a Project) and Copy link.

​

The Left Nav at a Glance

​

Test Cases: the Working List

Each row shows the case’s title, priority, latest status, and last run time. The toolbar holds Add More Tests, Edit Test (batch editing), and the run button, which doubles as an environment picker when the project has environments configured. Select rows to run, delete, or add them to a Test List in bulk. Editing, adding, and deleting are covered in Managing Test Cases.

​

Inside a Test Case

Clicking a row opens the test case as a drawer over the list; expand it to a full page when you need more room.

• Left, the definition: priority, the test description (the prompt the run is judged against), and the step list. The name is the heading and can’t be edited here; rename it in the batch editor (Edit Test). Edit steps opens the step editor; the primary button is Save & Run, because an edited test only means something once it re-runs.
• Right, the evidence: for UI tests, a Preview tab (the run’s recording) and a Code tab; for API tests, the generated code and its terminal output.
• Bottom, the run list: the Test runs panel lists this case’s past runs with status and date.

​

Reading a failure

Work through the evidence in this order:

1. The verdict and error message in the result panel: what the judge concluded, in plain language.
2. The step trace: which step failed, with the page state at that moment. For UI tests, see Step-by-Step Replay.
3. The output: terminal output for API tests, the recording for UI tests.
4. The fix-suggestion prompt: a ready-to-use prompt describing the failure. Copy it into Cursor, Claude Code, or your IDE and let your coding agent drive the fix.

After a change, saving the step editor or clicking Save & Run re-runs the case (for API tests, use Regenerate when the code itself must change). To re-check everything, run the whole project from the Test Cases toolbar. See Managing Test Cases for the details.

​

Test Runs & Reports

Test Runs lists every execution of this project. While a run is in flight you can watch it live; afterwards, its report sums up the results with AI analysis of what broke and why, and can be downloaded as a PDF.

​

Project Settings

​

Where to Go Next