The Team Testing Workload report enables you to report on the workload of your team based on assigned tests & sessions from selected milestones & runs.
The Team Testing Workload Report provides a consolidated view of your team’s testing activity, helping you understand how work is distributed across team members. By aggregating data from assigned tests and sessions linked to specific milestones and runs, the report highlights who is responsible for what, how much effort is involved, and where potential imbalances may exist.
Whether you're planning upcoming sprints, tracking team capacity, or communicating progress with stakeholders, this report enables you to make data-driven decisions with confidence. With flexible configuration options and a clear visual breakdown of workload, it’s an essential tool for managing test planning and ensuring efficient use of your testing resources.
The Team workload report configuration panel consists of 3 main areas, covered in each section below. Many of the configuration options correspond with controls in our existing PDF reports, which you can read more about in the guide: Flexible Print & PDF Reports - Export, Share & Review - Testmo
Generating the Report
The Options section controls the scope of the report to be generated, starting with project selection and gradually drilling down to further selections, enabling fine-grained control over objects to be included in the report.
Project
Use this dropdown to select which single project the report will cover. Reports can be generated for one project at a time, and cannot retrieve data from multiple projects in the same report.
Users
Use this dropdown to select which users you wish to include in the scope of the report. Report scope will automatically be constrained to users with access to the selected project. You may apply additional user or user-group level filters by selecting individual users or groups via the dropdown dialogs.
Milestone
Use this dropdown to select which milestones the report will cover. Only a single milestone may be selected and only the tests and sessions associated with the milestone will be displayed in the report.
Runs
The Runs dropdown enables you to make a quick selection as to whether you wish to include all active runs (the default setting) or no runs in the scope of your report. Alternatively, you can apply a filter to your runs by selecting the Filter option and clicking the filter icon. Note that filter settings applied in the Runs filter may be overridden by other option settings on the report.
Sessions
The Sessions dropdown enables you to make a quick selection as to whether you wish to include all active sessions (the default setting) or no session in the scope of your report. Alternatively, you can apply a filter to your sessions by selecting the Filter option and clicking the filter icon. Note that filter settings applied in the Sessions filter may be overridden by other option settings on the report.
Content
How much information the report will contain can be controlled using the Content settings. Check or uncheck the following controls depending on whether you want to display or omit the information accordingly:
Key metrics: This initial section of the report contains high-level metrics for the configured scope, in summary form. Depending on the options selected, the key metrics will display total numbers in the report for:
- The number of Users (or testers) in the scope of the report
- The number of Tests in the scope of the report, with an average number of tests per user
- The number of Sessions in the scope of the report, with an average number of sessions per user
Key metrics controls visibility of high level metrics for the configured scope
Workload chart: The workload chart displays test and session workload metrics for each tester included in the scope of the report. The chart display for each user may be comprised of the following bars:
- Tests & sessions: The number of tests & sessions assigned to the tester, stacked by tests then sessions, displayed visually to make it easy to assess how your testing workload has been distributed across testers. The precise number of tests and/or sessions may be seen by hovering over the bar section, or derived from the charts' x-axis, or by referring to the user statistics table.
- Estimate: The total estimated time to complete the assigned workload, based on the testers' estimates recorded against the tests and sessions in the report. Note that if estimates aren’t provided on some or all of the tests or sessions assigned to the user, Testmo won’t be able to calculate the estimated duration for completing them.
- Forecast: The total forecasted time to complete the assigned workload, based on Testmo’s observations of how long tests actually take to complete. Again, note that if estimates and actual testing durations aren’t recorded on your tests, Testmo won’t be able to calculate and attempt to predict this for you.
User statistics: Select the user statistics table for a breakdown of each tester's workload by area:
- Number of assigned Tests
- Number of assigned Sessions
- Total number of assigned Tests & Sessions
- Total time to complete Estimate
- Forecast time to complete
User assignments: A more detailed breakdown of workload for each tester can be seen in the User assignment cards.
- Workload statistics: Repeats the tests, sessions, estimated & forecast metrics made available in the Workload chart and User statistics table.
- Runs with assigned tests: Provides a list of runs in which the tester has been assigned tests, along with the number of tests assigned (per run), and the overall status of the run.
- Sessions assigned to user: Provides a list of sessions assigned to the tester, and the status(es) of each session.
Each section of the card can be enabled or disabled based on your reporting preferences, and the maximum number of runs or sessions limited to 20, 500, or 100.
Using the Report
Example: How can I spread my team’s testing workload more effectively?
Testmo’s Team testing workload report makes it easy to identify who is working on what, on your team. The steps below provide example settings for how you may answer the question of how to distribute your team’s work more optimally, in order to meet an aggressive deadline, for example.
Creating the report
On the Team testing workload report page:
- Select your project.
- Apply a user filter if necessary. In this example, we selected the QA & Development groups, since I want to see who has what workload.
- By default, Testmo unchecks the Include users without assignments checkbox. For this scenario, you’ll want to check it though, so you can see who doesn’t have any work.
- Select the milestone you’re working on. Release 2.1 in this example.
- Filter for active runs & sessions as needed. In this example, we’re interested in all active runs & sessions.
- Hit the generate report button. For my example, that presented us with the following, from which we can immediately see there are some problems:
I have 40 tests in total (25 cases & 15 sessions), and Arlie appears to be covering 33 of them. Some testers don’t have any work to do at all!
The User assignments card allows me to take a closer look, and click through to the relevant run(s) for some reassignments:
Reassigning tests and sessions more equitably gives me the following instead, evening out the distribution and bringing the estimated and forecasted duration right down in the process:
Report View Settings
The report view settings can be used to enable or disable components of the report so they can more easily be customised and shared to suit different use cases.
Show Links
By default, reports include links to the relevant pages in Testmo. For example, you can quickly navigate to tests by clicking their names. Or you can navigate to a test run by clicking its ID. Alternatively, if you want to share reports with persons who don’t have access to Testmo or shouldn’t even know where the tests are, you can completely disable and remove all links, so you can share reports without any links back to your Testmo account, by unchecking this option.
Show Persons
A major benefit of using Testmo for your projects is that it’s easy to track and understand which person on your team made changes to test cases or added results. Testmo also helps improve collaboration and task management by allowing you to assign tests to team members. If you don’t want to share that information in your report, however, you can easily hide all personal names and avatars by unchecking this option.
Show Header & Show Footer
Don’t want to include a header or Testmo-branded footer in your report? No problem, you can also disable those by unchecking this option.
Exporting & Sharing the Report
Once your report includes all the data and content you wish to include based on the settings above, you can share it with your team and stakeholders by clicking on the Print & PDF button.
Testmo utilises the built-in capabilities of your web browser to generate the Print or PDF version of your report, which you can send to your printer or save to a PDF using your browser controls.