Ask the Community
Closed test runs
The Closed Test Runs widget shows the number of test runs your team completed over time. It helps identify testing productivity and completion patterns.
Summary of widget data and visualization
This widget provides a visual summary of how many test runs have been closed within a given period, helping you understand the efficiency and productivity of your testing process. The line chart clearly displays the number of closed test runs over a selected timeline, making trends easy to spot.
Key metric information
- Closed Test Runs: The number of test runs fully completed and closed within a specific time frame.
- Horizontal axis (X-axis): Represents the timeline (dates).
- Vertical axis (Y-axis): Shows the count of closed test runs.
Data points clearly mark the number of test runs closed at specific intervals.
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. |
| CI runs only | Show only tests triggered by Continuous Integration (CI). |
To apply filters, click Add filter dropdown and select the applicable filters.
Use segments
Segments help you to compare two or more different sets of data side by side. To compare two or more closed runs, click Add segment. To learn more about segments, refer how to use segments documentation.
Use cases and actionable insights
The closed test runs widget enables teams to track and enhance test completion rates. Consistent review of closed runs helps maintain predictable and efficient testing cycles.
| Insight | Action |
|---|---|
| Easily spot spikes or drops in completed test runs. | If there is an unexpected drop, review recent team activities or resources. If there is a sudden spike, verify if testing practices changed. |
| Identify patterns or regular cycles in testing activity. | Use insights from testing cycles to plan future test schedules, ensuring smoother and predictable testing processes. |
| Check the impact of automated testing on your overall productivity. | UFilter by automated test runs to see their efficiency clearly. Decide where automation can further improve your testing strategy. |
Interpreting test data
Properly interpreting closed test run patterns helps your team maintain effective and timely test processes. Here are common scenarios to guide your analysis:
| If you see | It means | What to do |
|---|---|---|
| A sudden increase in closed runs. | A testing cycle or sprint recently ended. | Confirm with your team to ensure accurate reporting. Adjust resources for future cycles. |
| Consistent low numbers of closed runs. | Potential resource or efficiency issues. | Review test processes and address bottlenecks. Provide additional resources or training if needed. |
| Periodic fluctuations, such as weekly or monthly. | Regular cycles, like sprints or releases, dictate test closures. | Align future test planning around these predictable patterns to optimize productivity and results. |
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!