Track Tests | Testlio Help Center

The most basic indicators in the Tests Report you might want to track relate to the tests included in your QA efforts. They show how your testing has evolved and adapted, tracking the growth of new test cases and the archival of those that have served their purpose. Knowing how these indicators look helps you stay on track, balance priorities, and confidently drive improvements.

The indicators for tests in the Testlio Platform with example data.

Indicator	What It Tracks	What Signals It Might Bring
Active Tests	The total number of active tests during the period, which shows the ongoing scope of testing. Automatically compares with how many tests were active at the end of the prior period, showing progress or stability in test coverage.	A growing number of active tests might suggest the need for additional resources or more focus on automation to handle the increasing load. A shrinking number could indicate successful testing and issue resolution.
New Tests	How many tests were added during the period. Automatically compares to how many tests were added during the same time frame immediately before the period.	Tests are often added in response to new features, updates, or changes in requirements. A high number of new tests might suggest increased complexity or new features, prompting a review of whether the test strategy needs adjustment to maintain thorough coverage. A low number could suggest that the current coverage is stabilizing and resources can be redirected toward improving test quality or automation.
Archived Tests	How many tests were archived during the period. Automatically compares to how many tests were archived during the same time frame immediately before the period.	Archived tests provide insight into areas that may no longer need active attention, helping you streamline your testing efforts and focus resources on more critical or changing areas.
New vs. Archived Tests	A visual overview of how many new tests have been created and how many have been archived over time. This helps in understanding your team’s workload and the maintenance of your tests. The timeline is always on a weekly basis. To ensure accurate week-to-week comparisons, make sure your date range starts at the beginning of a week.	This indicator helps demonstrate how the testing scope evolves over time. A healthy balance between new and archived tests shows that while new functionalities are being tested, older, stable components are being archived as no longer needed. This shows that system is under continuous refinement and testing efforts are focused on both innovation and maintaining a stable foundation.
Average Steps per Test	The average complexity of tests, as shown by the average number of steps.	A high average could indicate that tests are too granular or complex, which may require a review to simplify and optimize. Bear in mind that more complex systems require equally complex tests. A low average may suggest the need for deeper testing in certain areas.
Breakdown by Priority	The distribution of active tests at the end of the period across priority levels.	Greater focus on high-priority tests may indicate that the most critical features are being safeguarded. Balance across all priorities may show a well-rounded focus. Imbalances can help show a need to redirect resources to higher-priority areas that need more attention.
Automated Tests	The percentage of all tests that have been automated.	Higher automation means faster feedback loops and scalability. Automation is driving quicker testing and reducing manual effort. A low percentage may show initial efforts to move forward with automation If the automation percentage hasn’t grown recently, it may indicate that something is blocking the pipeline and needs investigation. If the automation percentage remains low, this suggests a need to review your automation strategy. By identifying areas where automation can be expanded, you can improve test execution speed and free up manual testers for more exploratory or complex tests.

Follow Test Updates

In addition to tests themselves, you can keep track of updates made to tests. You can also filter these indicators for a specific date range and/or specific workspaces.

These indicators highlight how your tests are evolving, ensuring that nothing gets outdated. By tracking updates, you’ll see just how responsive and proactive your testing process is, making sure every test stays sharp and ready for action.

A chart comparing updated tests and total updates made.

Indicator	What It Tracks	What Signals It Might Bring
Updated Tests	The number of tests modified within the period. Automatically compares to how many tests were modified during the same time frame immediately before the period.	Tracking updated tests helps you assess how your tests are staying relevant and up-to-date with evolving features or requirements. Frequent updates may indicate a highly dynamic system and that you may need to adjust resource allocation to keep up with changes. Fewer updates could suggest stability and an opportunity to focus on optimization or automation.
Avg. Weekly Updates	The average number of updates made to tests per week during the period. Automatically compares to weekly updates during the same time frame immediately before the period.	This metric shows the consistency of test case maintenance over time. A steady or increasing number of updates may indicate that testing is being regularly reviewed and refined, ensuring that it keeps pace with project demands and system updates. A drop-off could suggest a need to revisit test coverage or reprioritize areas that may have been put out of scope or on hold.
Total Updates Made	The cumulative number of updates made to all tests during the period.	Total updates reflects the overall effort the team is putting into maintaining and optimizing the test suite. A high number of updates could point to an evolving system that requires more attention. A low number might suggest a mature, stable system that allows for focusing on other areas such as automation or exploratory testing.
Updated Tests vs. Total Updates Made	A visual comparison of the number of unique tests that have been modified versus the total updates made within the period. This helps you monitor both the breadth (number of tests updated) and the depth (total updates made) of changes.	This chart can help you identify patterns in test maintenance and ensure that your testing process adapts to evolving requirements. A large discrepancy between the two numbers may signal that certain high-impact areas are getting more attention. Significantly more total updates than updated tests may reflect a commitment to quality and active refinement of tests to adapt to changes. A closer ratio might suggest a broad, system-wide approach to maintenance. This insight can help you decide whether to focus on refining key test cases or reallocating efforts to cover more ground across the entire suite.

Monitor Execution Trends

Understand Test Workload

Track Issues

Track Runs

Monitor Manual Testing