You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/project/runs/managing-runs.md
+40-15Lines changed: 40 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -199,7 +199,7 @@ In this case, your Test Run will open in Manual Run window, allowing you to manu
199
199
### Advanced Relaunch
200
200
201
201
The **'Advanced Relaunch'** option offers more flexibility when relaunching tests.
202
-
It allows you to select specific tests to relaunch, instead of repeating the full test run. This enables more targeted, efficient workflows — whether you’re rerunning failed tests or just need to retest a subset of scenarios.
202
+
It allows you to select specific tests to relaunch, instead of repeating the full run. This enables more targeted, efficient workflows — whether you’re rerunning failed tests or just need to retest a subset of scenarios.
203
203
204
204
**'Advanced Relaunch'** option is available for all types of test runs.
205
205
@@ -219,29 +219,56 @@ In the opened sidebar window, configure your relaunch (optional):
|**Run ID**| A new run is created with a new ID. The original run remains unchanged. | The original run is reused — same run ID. |
229
+
|**Selected tests**| Only selected tests are included in the new run and reset to Pending status (unless **Keep values** is enabled). | All tests are included with their current statuses kept. Only selected tests are reset to **Pending** status. |
230
+
|**Unselected tests / Select all**| All tests are reset to Pending status in the new run (unless **Keep values** is enabled). | All tests retain their existing results. |
231
+
222
232
:::note
223
233
224
-
Only selected test cases will be relaunched for manual re-check or automatically re-run on CI.
234
+
When re-running tests, selecting **Select all** or leaving no tests selected produces the same result: all tests in the run are included automatically.
225
235
226
236
:::
227
237
228
-
If you have many test cases and need to select all of them or only failed ones, you don't have to do it manually. You can use the **'Select'** feature.
238
+
#### Keep Values
229
239
230
-
**There are two options of how you can select all tests, depending on your needs:**
240
+
The **'Keep values'** option is only available when **'Create new run'** is enabled. It controls whether test results are carried over into the new run.
231
241
232
-
1. Use **'Checkbox Select'** option by simply clicking on checkbox. This is useful if you want to select a group of tests (like all filtered failed tests) and then manually unselect or add more. With this option, you can easialy edit your selection.
2. Use the **'Select All'** option from the **'Select'** dropdown. This is a quick way to select all currently displayed test cases. With this option, you cannot manually add or remove tests from the selection. If you change the filtering, the selection will automatically update to include only the currently displayed tests. Use the **'None'** option to unselect all tests.
249
+
There are two ways to select all tests for relaunch — the top-level **Checkbox** and the **Select All** option from the dropdown.
|**No filter applied**| Selects all tests in the run — passed, failed, and skipped. | Selects all tests in the run — passed, failed, and skipped. |
254
+
|**Filter applied (e.g. failed only)**| Selects only tests matching the active filter. Tests outside the filter are not included. | Selects only tests matching the active filter. Tests outside the filter are not included. |
255
+
|**Switch to another filter**| The previous checkbox selection is cleared only when tests are selected in the new filter. | Selection updates automatically to the new filter. Previous selection is cleared. |
256
+
|**Add individual tests manually**| Individual tests from other statuses can be added manually. All selected tests are included in the relaunch. | Individual tests cannot be added or removed manually. |
257
+
|**Clear selection**| Uncheck the checkbox. | Use **'None'** from the dropdown. |
258
+
259
+

260
+
261
+
:::note
262
+
263
+
When using the Checkbox, only the tests that are loaded on the page are selected — scroll through the full list first to ensure all tests are included.
264
+
265
+
:::
239
266
240
267
**Key benefits of Advanced Relaunch:**
241
268
242
-
- Customize relaunches to better fit your team's workflow.
243
-
- Simplify recovery after CI failures or flaky test results.
244
-
- Avoid redundant test executions and manual reconfiguration.
269
+
- Customize relaunches to better fit your team's workflow
270
+
- Simplify recovery after CI failures or flaky test results
271
+
- Avoid redundant test executions and manual reconfiguration
245
272
246
273
## How to Launch a Run Copy
247
274
@@ -397,11 +424,10 @@ Pulse displays different activity messages depending on how the Run was removed:
397
424
398
425
1.**Automatic purge**
399
426
When a Run is purged automatically by the system due to expiration, Pulse records an entry similar to:
400
-
*“Manual tests at 20 Nov 2025 11:56 have been purged by system on expiration (moved to Archive).”*
427
+
_“Manual tests at 20 Nov 2025 11:56 have been purged by system on expiration (moved to Archive).”_
401
428
2.**User-initiated purge**
402
429
When a Run is purged manually, Pulse records the event:
403
-
*“Manual run has been purged by user (moved to Archive).”*
404
-
430
+
_“Manual run has been purged by user (moved to Archive).”_
405
431
406
432
3.**Permanent deletion from Archive**
407
433
When a Run is permanently removed from the Archive, Pulse displays the event indicating that the manual run has been permanently deleted.
@@ -410,7 +436,6 @@ Pulse displays different activity messages depending on how the Run was removed:
410
436
411
437
These Pulse records provide a clear audit trail for all purge-related actions, mirroring the two-step deletion flow and ensuring accountability across both manual and automated processes.
412
438
413
-
414
439
### Summary
415
440
416
441
By introducing the Purge option, Testomat.io ensures that Run data is handled with more safety and flexibility. You can keep your workspace clean and optimize storage, while still maintaining the ability to restore important Runs from the Archive when needed.
0 commit comments