Skip to main content
Monitor Execution Trends
Aaron Collier avatar
Written by Aaron Collier
Updated over 2 months ago

These indicators in the Tests Report track how often tests are run, where the focus lies, and whether critical areas are getting the attention they deserve.

Example execution indicators in the Testlio Platform.
A chart comparing test executions by priority and the number of testers.

Indicator

What It Tracks

What Signals It Might Bring

Test Executions

Shows the total number of test executions in the period. Automatically compares to how many tests were executed during the same time frame immediately before the period.

This metric helps you track testing activity.

  • Increasing executions may indicate a growing or evolving system, prompting a review of resources or automation to handle the load. It may also signal increased testing coverage.

Unique Test Executions

The count of unique tests that have been run.

  • More unique tests suggests broad test coverage.

  • Fewer unique tests may signal the need to diversify or add new tests to ensure comprehensive testing.

Avg. Executions per Test

How many times each test has been executed on average.

  • A high average might indicate areas of the system that require frequent retesting, prompting consideration of automation.

  • A low average may suggest certain areas might required greater focus.

High-priority Executions

The number of test executions categorized as high priority.

This metric shows whether critical areas are being sufficiently tested.

  • Few high-priority executions may suggest the need to shift focus to more vital parts of the system.

    • This situation could also come from strategy change or performance and stability improvement.

Breakdown by Priority

The distribution of test executions across priority levels.

This metric helps you identify where testing efforts are concentrated based on priority, giving insight into how risk is managed and resources are focused.

  • Greater focus on high-priority tests may indicate that the most critical features are being safeguarded.

  • Greater focus on low-priority tests may indicate a need to reallocate resources toward high-priority tests.

Medium Priority Executions

The number of test executions categorized as medium priority.

This metric shows whether important but not critical areas are being sufficiently tested.

  • Many medium-priority executions may suggest the need to shift focus to more vital parts of the system.

  • Few medium-priority executions may suggest the need for more attention to these areas to prevent mid-level risks from escalating.

Test Executions by Priority vs. Testers

A visual representation of test executions categorized by priority (high, medium, low, and unset) over time alongside the number of testers involved.

This chart helps you track the balance between test execution load and tester resources. You can monitor how well different priority levels are being covered and whether tester allocation aligns with the testing demands.

  • Many testers and few tests may indicate a need to test on more devices and testers or a need for optimization.

  • Few testers could indicate that too much work is being put on individual testers and a need to optimize the workload and number of testers.

Did this answer your question?