Understand Test Workload | Testlio Help Center

These indicators in the Tests Report provide valuable insights into how efficiently your testing hours are being managed and whether there are any patterns in use.

Example workload indicators in the Testlio Platform

A heat map in the Testlio platform showing what days are the busiest in terms of manual testing hours, with those days being darker in color

Indicator	What It Tracks	What Signals It Might Bring
Test Execution Hours vs. Total	The percentage of time spent on manual testing within total logged hours (includes all work logged with the Testlio Services Taxonomy, including automation and client services). Automatically compares to the equivalent percentage during the same time frame immediately before the period.	This indicator helps understand the focus on manual efforts versus other activities, giving insight into how testing resources are being utilized. The signal being sent varies depending on the exact engagement. For example, projects with more automation should see lower percentages. Tracking trends in utilization helps make sure the testing strategy is meeting needs.
Test Execution Hours	The total hours spent on manual testing during the period. Automatically compares to the hours during the same time frame immediately before the period.	This metric shows how much manual attention the product is receiving. It indicates the team’s effort and commitment to thoroughly reviewing the product. Stable hours consistently at the maximum might indicate a need to reassess whether additional resources might be needed.
Total Hours	The total logged hours (includes all work logged with the Testlio Services Taxonomy, including automation and client services). Automatically compares to the hours during the same time frame immediately before the period.	This indicator shows how much work is being done outside of manual testing. Tracking total hours helps the team ensure that time is being allocated effectively across all project activities, not just testing.
Busiest Day	The day of the week with the most test execution activity.	This data point offers insight into team rhythms and resource planning. Knowing the busiest day allows for better planning and resource allocation. If testing activity is consistently higher on a particular day, the team can ensure that enough testers are available to handle the workload efficiently.
Test Execution Hours per Run	The average time spent on manual testing per run. Automatically compares to the average during the same time frame immediately before the period.	This metric helps evaluate the efficiency of each test run. A high average may show in-depth testing and may also be an opportunity to streamline processes or introduce automation. A low average might indicate quick, efficient testing or show a need to assess whether enough attention is being given to each run.
Total Hours per Run	The total average time spent per run (includes all work logged with the Testlio Services Taxonomy, including automation and client services). Automatically compares to the average during the same time frame immediately before the period.	This metric helps assess the balance between efficiency and coverage. Fewer hours might show a need to review whether testing is comprehensive enough to meet quality standards, ensuring no areas are being overlooked. More hours might reveal an opportunity to dive into whether the time spent is hitting critical areas or if adjustments in focus are needed.
Busiest Day (Heat Map)	A visual representation of testing activity over time.	The heat map helps identify trends in peak testing across days and weeks, aiding in identifying peak testing periods and guiding resource allocation. Certain days or weeks being consistently busy can help shape testing plans, ensuring that enough testers are available to handle the load. This indicator also provides insights into workload distribution, allowing optimization of effort and avoiding potential bottlenecks or overburdening testers during high-activity times.

View Testing By Location

These indicators give you a global perspective on where testing is happening and how your product is performing in different regions. They help ensure your product is being tested across diverse environments, helping you optimize coverage and address any region-specific concerns along the way.

A map of the world with circles in various locations of different sizes and colors representing the top test locations, also given by name in a table

Indicator	What It Tracks	What Signals It Might Bring
Tests by Location	A visual representation of where testing took place during the period. The size of the circles represents how many tests were conducted and the color shows the failure rate (green represents successful tests and red represents failed tests).	This chart helps identify where testing resources are concentrated and whether there are any gaps in geographical coverage. Locations with high failure rates may to region-specific issues such as localization bugs or environment-related problems that need attention. Regions with small circles may be good candidates for expanded testing.
Top Test Locations	A list of the countries with the most tests executed during the period.	This list can help identify where most testing is taking place and how the product is being validated in different environments. It helps with optimizing resource allocation, ensuring that testing efforts are effectively distributed to cover all critical regions and that any regional issues are promptly addressed. Certain regions having significantly higher volumes could indicate a need to balance resources or investigate why other regions have less coverage.

Track Tests

Monitor Issues and Severity Levels

Understand Issue Workload

Track Runs

Monitor Manual Testing