Ask the Community
Active test runs
The active test runs widget shows the current status of all active test runs. It helps you quickly see if tests are passing, failing, blocked, or need attention.
Summary of widget data and visualization
This widget presents the current status of test cases using easy-to-understand metrics and a clear visual chart. It helps you quickly identify how many tests have passed, failed, or need attention.
Key metric information and visualization
Colors represent different test case statuses. Hover over any color to see exact numbers and percentages. The doughnut chart shows the distribution of test results. Each section clearly displays the number and percentage of test cases in each status.
| Color | Status | Description |
|---|---|---|
| N/A | Total Test Cases | The number of test cases currently running. |
| Green | Passed | Tests that ran without issues. |
| Red | Failed | Tests that found issues needing fixes. |
| Grey | Untested | Tests that have not started yet. |
| Orange | Skipped | Tests intentionally not run. |
| Yellow | Retest | Tests marked to run again. |
| Purple | Blocked | Tests that cannot run because of other problems. |
Available filters
Apply the following filters to narrow-down to specific test runs based on your criteria.
| Filter | Description |
|---|---|
| Test Run Owners | Show test runs by the responsible team member/owner. |
| Test run tags | Use match all or match any one value to filter tests with specific labels. |
| Test run types | See only manual tests, automated tests, or all types of test runs. |
| Unique test run name | Filter by a specific test run. |
| Branch | Show tests associated with a particular code branch. |
| Test Case Status | Focus on a specific status, such as passed, failed or blocked tests etc. |
| CI runs only | Show only tests triggered by Continuous Integration (CI). |
To apply filters, click Add filter dropdown and select the applicable filters.
Use cases and actionable insights
The active test runs help you keep projects on track by identifying test statuses clearly. It enables quick decisions and clear actions for everyone involved in software testing, regardless of role or experience.
| Insight | Action |
|---|---|
| Quickly spot how many tests are failing or blocked. | Click directly on the doughnut chart segments for Failed or Blocked tests. This opens detailed results, letting you identify and fix issues promptly. |
| See if many tests remain untested or skipped. | Evaluate if tests are delayed or intentionally skipped. Discuss with your team to confirm if these tests should run now or later. |
| Understand testing health across specific code branches. | Use filters to select a branch. Immediately see if recent changes have caused new problems or resolved existing issues. |
Interpreting test data
Interpreting test data correctly helps you respond quickly and accurately. Here are simple guidelines to understand common patterns in the test results:
| If you see | It means | What to do |
|---|---|---|
| A sudden increase in tests marked as Failed. | A recent update introduced bugs. | Immediately review recent code changes and address the issue. |
| Many tests with the Blocked status. | There is a dependency issue, such as a service outage or missing resource. | Identify and resolve the external blockage or alert the responsible team promptly. |
| Consistently high numbers of Retest or Skipped tests. | Tests are being deferred or avoided unnecessarily. | Verify test priorities with your team. Clarify when these tests need to run, ensuring critical tests are not overlooked. |
Using these insights ensures testing remains accurate, timely, and effective.
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!