Managing Runs

Testomat.io offers comprehensive features for managing test runs, catering to both manual and automated testing. Here’s how to manage runs within the system:

1. Update Test Runs: Add new test cases directly from Test Run, Relaunch finished Test Runs to update tests statuses, or Launch a copy. Find more information in the sections below.

2. Filter Test Runs: Filter runs and share the filter parameters with your teammates directly via URL. find more information added in the sections below.

3. Group Runs: Organize your runs into RunGroups based on criteria like sprint, release, functional area, or any other logical grouping. Read more on the RunGroups page.

4. Select a Merge Strategy: Aggregate the results of the individual test runs within a RunGroup. Find more information on the Merge Strategies page.

5. Archive Runs & RunGroups: Maintain a clean and organized main board tailored to your ongoing testing priorities. Read how to archive Runs & RunGroups on the Archive Runs & RunGroups page.

6. Share Run Reports: Share test results with your teammates or stakeholders. You can find detail information about Reports on the Run Reports page.

How to Create a Test Case within a Run

You can create test cases directly within a test Run, avoiding additional navigation and ensuring the new tests are automatically included in the associated test plan.

1. Go to the ‘Runs’ page.
2. Start the desired test run.
3. Scroll to the bottom of the test suite.
4. Click the ‘Create test’ button.

5. Enter the test case details in the provided field.
6. Click the checkmark ✔️ icon to add the new test case, or the X icon to discard it.

Note

The ‘Create Test’ button can be hidden via the ‘Hide Test Creation’ option in the ‘Extra menu’ dropdown menu.

Use Cases for Creating Test Cases Within a Run:

• Identifying gaps in test coverage during execution: While performing manual testing, a tester discovers an untested scenario. They can instantly add it to the run and repository without switching context.
• Capturing exploratory test cases: Testers conducting exploratory testing can log and formalize new test cases as they go, ensuring useful insights are not lost.
• Collaborative test planning in real time: During team sessions or test reviews, testers can collectively identify and add new tests based on discussion or observed issues.

Test Case History

When you launch a test run and make changes to test case title or description, a new entry is added to the test case’s history. This entry records who made the edit and when it occurred.

1. Navigate to the ‘Runs’ page.
2. Launch a new Run or continue an existing Run.

3. Click the ‘Extra menu’ button next to the test case you want to edit.
4. Select Edit.

5. Modify the test case title or description as needed.
6. Click Save to apply the changes.

7. The new history entry will appear directly in the test case block, showing who edited the test case and the date and time of the change.

Note

The test case history is only available while the test run is in progress.

How to Pin a Run or RunGroup

Testomat.io allows users to pin RunGroups or individual Runs to the top of the Dashboard for quick access to critical or frequently used tests or test runs, helping teams stay focused on the most relevant tasks. This supports faster navigation, improved focus, and customizable workflows — ideal for monitoring regression tests, environment-specific runs, or production hotfixes.

Use Cases for Pinning:

• Faster Access: Quickly access important or active test runs without searching through lists. Example: Pin ongoing regression tests for easy monitoring during a sprint.

• Improved Focus: Keeps high-priority RunGroups or Runs in view, reducing distractions. Example: Pin runs for specific environments or features during critical phases.

• Customizable Dashboard: Tailors the Dashboard to individual team workflows and priorities. Example: Pin runs related to production hotfixes or high-impact bugs.

To Pin Run or RunGroup:

1. Go to the ‘Runs’ page.
2. Find the Run or RunGroup you want to pin.
3. Click the ‘Extra menu’ button aligned next to the item.
4. Choose ‘Pin’ from the dropdown options.

The ‘Pin’ option is also available in the detailed run view menu.

The selected Run or RunGroup will now appear pinned at the top of the list for quick and easy access.

How to Relaunch Runs

For some reason, you may need to re-check some tests in your Run. Testomat.io offers several options to relaunch your Test Run, depending on the run type and your needs.

Basic Relaunch for Manual Run

Select the basic relauch option to restart your manual test run with all test cases and their current statuses:

1. On the ‘Runs’ page, select the run that you need to re-check.
2. Click the ‘Extra menu’ button.
3. Select ‘Relaunch’ option from the dropdown menu.

The ‘Relaunch’ option is also available on the main Dashboard.

Your Test Run will open in Manual Run window, allowing you to re-check tests and change their statuses:

When finished, click the ‘Finish’ button. You will see tests with new statuses and updated Run Report.

Your Test Run will also contain updated information on its results, including a changed tag and Run status.

Relaunch Failed Test Cases for Automated Runs

For your automated or mixed runs, select ‘Relaunch Failed on CI’ option to relaunch only failed test cases from the selected run.

1. On the ‘Runs’ page, select the automated or mixed run that you need to re-check.
2. Click the ‘Extra menu’ button.
3. Select ‘Relaunch Failed on CI’ option from the dropdown menu.

After selecting ‘Relaunch Failed on CI’ option, failed automated test cases will automatically re-run on CI and Manual Run window will open for re-checking manual failed test cases. The same test run with updated statuses will be displayed after run is finished.

Relaunch All Test Cases for Automated Runs

For your automated or mixed runs, you can also select ‘Relaunch All on CI’ option to relaunch all test cases from the selected run.

1. On the ‘Runs’ page, select the automated or mixed run that you need to re-check.
2. Click the ‘Extra menu’ button.
3. Select ‘Relaunch All on CI’ option from the dropdown menu.

All automated tests cases will automatically re-run on CI. If you relauch mixed run, your Test Run will open in Manual Run window and you will be able to re-check manual tests and change their statuses, while automated test cases re-run on CI simultaneously.

Relaunch Automated Runs Manually

With ‘Relaunch Manually’ option you can as well re-check your automated test cases manually.

1. On the ‘Runs’ page, select the automated or mixed run that you need to re-check.
2. Click the ‘Extra menu’ button.
3. Select ‘Relaunch Manually’ option from the dropdown menu.

In this case, your Test Run will open in Manual Run window, allowing you to manually re-check all tests (manual and automated) and change their statuses if needed.

Advanced Relaunch

The ‘Advanced Relaunch’ option offers more flexibility when relaunching tests. 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.

‘Advanced Relaunch’ option is available for all types of test runs.

1. On the ‘Runs’ page, select the run that you need to re-check.
2. Click the ‘Extra menu’ button.
3. Select ‘Advanced Relaunch’ option from the dropdown menu.

In the opened sidebar window, configure your relaunch (optional):

1. Enter a custom run title.
2. Enable ‘Create new run’ option (if needed).
3. Enable ‘Keep values’ option (available only if ‘Create new run’ is enabled; this shows previous statuses for test cases).
4. Select the tests that you want to include in your relaunched run (use filtering, sorting, or search options).
5. Click the ‘Relaunch’ button.

Only selected test cases will be relaunched for manual re-check or automatically re-run on CI.

Key benefits of Advanced Relaunch:

• Customize relaunches to better fit your team’s workflow.
• Simplify recovery after CI failures or flaky test results.
• Avoid redundant test executions and manual reconfiguration.

How to Launch a Run Copy

If you need need to re-check tests in your Run, but for some reason, you want to save this Test Run separately, use the ‘Launch a copy’ option.

To Lauch a Run Copy you need:

1. On the ‘Runs’ page, select the run that you need to copy and re-check.
2. Click the ‘Extra menu’ button.
3. Select ‘Launch a Copy’ option from the dropdown menu.

The ‘Launch a Copy’ option is also available on the main Dashboard.

Your Test Run will open in Manual Run window, allowing you to re-check tests and change their statuses:

When finished, click on ‘Finish’ button. A new Test Run with new test statuses and a new Run Report will display:

On the main Runs Dashboard, you will see both Tests Runs: the original run with old test results and the copy with new test results.

Multiselection For Runs

Multiselection allows the bulk application options to many runs with one click. Click the ‘Multi-select’ icon and select a few runs to see multi-select menu panel.

Multi-select Options Overview:

1. ‘Select all’ - select all runs on the Runs page.
2. ‘Archive’ - archive selected runs.
3. ‘Labels’ - apply/remove labels from runs.
4. ‘Compare’ - open Compare runs view.
5. ‘Extra menu’ - access additional options.
6. ‘Delete’ - delete selected runs.

Click the ‘Extra menu’ button on multi-select menu panel to see additonal options:

1. ‘Link’ - link selected runs to JIRA, GitHub, Azure,Linear or other issues management system.
2. ‘Download’ - export selected run reports to spreadsheet.
3. ‘Merge’ - merge selected runs (read more in the Merge runs section).
4. ‘Move’ - move Runs to/from RunGroups.

Filtering Test Runs

Testomat.io provides filtering capabilities for Runs and RunGroups. On the Runs page, you can find Basic filters and Additional filters.

Filter Runs by TQL

Testomat.io Query Language (TQL) for Runs enables more flexible searches, allowing users to filter Test Runs by criteria like finished_at, passed_count, has_test_label and many others. This helps quickly find relevant runs and improves test analysis.

Visit a separate section of the documentation - Runs Variables, if you want to find out more about the Runs Variable.

Share Runs Filter

This feature allows you to pass Runs and Runs Archive filter parameters directly through the URL. This improves collaboration by enabling teams to quickly access relevant test results without manually adjusting filters.

Specify the necessary filtering parameters on the Runs or Runs Archive page, then copy the URL and share it with interested members.