Test runs

A run records how cases were executed — who worked them, what result each got, and any reruns. Open a run from the runs list or from the History tab.

Work a run

Select results in the run tree. Bulk actions cover:

• Assign — pick one or more members for the selected results. One member gets all of them; several members share them as evenly as possible
• Set result — apply a status to the selected results
• Rerun — rerun the selected results; reruns stay linked to the run

Changing a result’s status on a rerun updates that result’s status on the parent run.

Result card

Open a result. The result card tabs are Steps, Env, History, and Reruns. The result card sidebar holds the result, assignee, and related case metadata.

Steps

On Steps, you can set a status on individual scenario steps. Step statuses and the result status stay linked both ways: changing a step updates the result, and changing the result applies that status across the steps. The card can show files, error logs, and comments; comment text supports rich formatting.

For automated results, Compare steps matches the result steps with the linked test case.

Env

Env shows the environment variables the autotests ran with. The tab appears only for automated results that include at least one variable.

Lock

Lock a run seals that run, its results, and its reruns against changes until you Unlock. Auto-cleanup does not delete locked runs.

Analytics

In the run header, open Analytics to see charts for this run: Summary, Automation, Duration, and Assignees. Trends across the project live under Analytics in the project menu.

Related: Test plans.