Every Test Set has its own dedicated page where you can see its composition, run history, and key stats in one place.
How to open a Test Set
Click any row in the Test Sets list (outside the action buttons). The detail page opens automatically.
Use the browser back button or the breadcrumb at the top to return to the Test Sets tab.
Test Cases tab
The Test Cases tab shows all Test Cases assigned to this Test Set in a table.
Click a row to open the Test Case.
Use the Add Test Cases button in the header to assign Test Cases via a searchable popover.
Remove a Test Case from the set using the Remove from set action in the Actions column.
Empty state: If no Test Cases are assigned yet, an illustration and an Add test cases button appear.
Execute a Test Set
Click Execute in the header. The execution settings dialog opens on the saved settings of the Test Set, or on Per test when the set has none. Start the run. The Set Runs tab shows the new run. A change in the dialog applies to this run only.
Note: The Execute button is disabled when the Test Set has no Test Cases.
Set Runs tab
The Set Runs tab shows all runs scoped to this Test Set.
Click a row to open the Test Run Report.
Runs are paginated.
Empty state: If no runs exist yet, an Execute test set button is shown.
Re-execute the failed tests of a run
A Test Set run works as a test campaign. When some Test Cases of a run do not pass, you can run only those Test Cases again. The Test Cases that passed keep their result.
Open the Set Runs tab.
In the row of the run, select Re-execute failed tests.
Check the execution settings, then start the run.
Each Test Case of the run that did not pass runs again. Its new result joins the same Test Set run, and the status and the pass rate of the run update when it finishes. Inside the run, a Test Case that ran again lists its attempts: Attempt 1, Attempt 2, and so on.
To run one Test Case again, expand the run and select Re-execute in the row of that Test Case. To run several, select their rows, then select Re-execute in the bar that appears. Their results also join the same run.
When the Test Set has a pre-requisite, the pre-requisite runs again first, and the Test Cases that you re-execute wait for it, as in a full run of the set. See Test Set Pre-requisites.
The same actions work in the main Test Runs tab of the project.
See where the time of a run went
The Duration of a finished Test Set run is the time from the start of its first test to the end of its last test. Tests that run at the same time count once. To see how the duration splits, put the pointer on the duration in the row of the run. A card opens after a short delay. Select the duration to keep the card open. Press Escape or click outside the card to close it. With the keyboard, go to the duration cell and press Enter or Space.
At the top of the card, next to Time spent, Started after shows the time from the launch of the run to the start of its first test. This time is not part of the duration.
The card then shows these lines:
First run: the time of the first attempt of each Test Case.
Re-runs: the time that automatic retries and re-executions add, with the number of Test Cases that ran more than once. A re-run that ran at the same time as other tests adds no time. This line shows only when a Test Case ran more than once.
Between tests: the time in which a test waited in the queue for the previous tests to end, or in which an automatic retry waited before it started. This occurs mostly when the tests run one after the other. This line shows only when there is such a wait.
Duration: the sum of First run, Re-runs and Between tests.
Without parallel runs: the time of all attempts, added one after the other. This line shows only when it is longer than the duration, that is, when some tests ran at the same time.
When you re-execute a Test Case later, for example on the next day, only the time of the new attempt adds to the duration. The time between the end of the run and the re-execution does not count.
The card is available in the Set Runs tab and in the Test Runs tab of the project. A run that is still in progress and the run of a single Test Case have no card. If a Test Case of the run is still queued, running or paused, the card tells you that its time is not counted yet.
Properties panel
Click the panel icon in the header to show or hide the Properties panel on the right side.
The panel has two tabs: Properties and Execution settings. The Execution settings tab saves the execution settings of the set. See Manage Execution Settings.
The panel displays:
Last run: timestamp, status badge, and who launched it
Created / Updated dates
Description
Health: pass/fail ratio across the last 5 runs
From the panel you can also:
Copy ID: copies the Test Set UUID to your clipboard
Copy title as link: copies a markdown link to the Test Set
Copy link: copies the full URL of the detail page
Delete: shows a confirmation dialog, then returns you to the Test Sets list
Rename a Test Set
Click the title in the header to edit it inline. Press Enter or click away to save. An empty name is not accepted.
Troubleshooting
The Execute button is greyed out.
The Test Set has no Test Cases. Add at least one Test Case before running.
A Test Case disappeared from the set.
It may have been removed via the Remove from set action. Re-add it using the Add Test Cases button.
I can't find a past run.
Runs on the Set Runs tab are filtered to this specific Test Set. Runs across all sets appear in the main Test Runs tab of the project.
Re-execute failed tests shows "No failed test cases to re-execute".
Every Test Case of the run passed, so there is nothing to run again.
The row of a run has no Re-execute failed tests action.
The run is still in progress. The action appears when the run finishes.
The duration of a run does not open a card.
The run is still in progress, or the row is the run of a single Test Case. The card is available when the Test Set run finishes.
The duration is shorter than the time of all the tests added together.
Tests that run at the same time count once in the duration. The Without parallel runs line of the card shows the time of all the tests, added one after the other.
A re-executed Test Case adds 0s to the duration.
It ran at the same time as other tests of the run, so the run did not take longer.
The Schedules tab
The Test Set detail page carries three tabs: Test Cases, Set Runs and Schedules, each showing a count of what it holds.
Schedules lists the recurring rules attached to this Test Set, with the frequency, the Environment and Persona each runs as, the next and last run, and the status. A red dot beside the tab name means at least one Schedule has been paused automatically, so a problem is visible without opening the tab.