Test execution distribution
See how execution work is spread across users for manual or automated test runs, and find uneven workload before a run closes.
The test execution distribution widget draws one horizontal bar per user. Each bar is that userβs execution count, split into segments by execution status. Use it to find uneven workload before a run closes.

Summary of widget data and visualization
The widget plots users on the vertical axis and execution counts on the horizontal axis. Rows are sorted from the highest execution count down to the lowest. The busiest user is always first.
Key metric information and visualization
The following table describes each element of the chart:
| Element | Details |
|---|---|
| Row label | The user the row belongs to. |
| Bar length | That userβs total execution count across the executions that match your filters. |
| Bar segment | One execution status. The segment length is the count of executions in that status. |
| Horizontal axis | The execution count. |
| Tooltip | Hover over a segment to read the user, the status, and the execution count. |
Test run type
Test run type decides which executions the widget counts. Set it first, because it changes both the Group by options and the filter list. The following table shows what each type covers:
| Test run type | Executions counted | Group by options |
|---|---|---|
| Manual | Executions from manual test runs. This is the default. | Assignee or Last Executed By |
| Automated | Executions from automated test runs. | Last Executed By |
Switching the test run type clears the filters you already added. Each type carries its own filter set.
Group by
Group by decides what each row represents. Choose one of the following options:
- Assignee groups executions by the user the test case is assigned to. This is the default for manual runs.
- Last Executed By groups executions by the user who ran the test case most recently.
Manual executions that have no assignee are grouped under Unassigned.
Available filters
Filters narrow which executions the widget counts. The filter list depends on the Test run type you selected.
To add a filter, click Add filter and select the filter you want. To reuse a filter set from another widget on the dashboard, click Import from other widgets. After you add the first filter, Clear filters appears next to Filters. Click it to remove every filter.
Some filters carry a match operator to the left of the filter name. Use it to set how multiple values combine. Matches any one value (OR) is the default, and it counts an execution that matches any value you selected. When a filter also offers Matches all values (AND), that option counts only the executions that match every value you selected.
Some filters also cap how many values you can select. When a cap applies, the widget states it under the filter as soon as you add the filter.
Filters for manual test runs
Apply the following filters when Test run type is set to Manual:
| Filter | Details |
|---|---|
| Projects | The projects the test runs belong to. |
| Folders | The test case folders that hold the executed test cases. |
| Test run tags | The tags applied to the test runs. |
| Test Case Tags | The tags applied to the test cases. |
| Unique Run Name | A named test run. |
| Test Case Status | The execution statuses to include, such as Passed, Failed, or Untested. One widget holds up to 20 statuses. |
| Assignees | The users the test cases are assigned to. One widget holds up to 30 assignees. |
| Last executed by | The users who last updated the test result. One widget holds up to 30 users. |
Use the Folders filter to read distribution for one module instead of a whole project. Click Select Folders, choose a project, then select the folders you want. Selecting a parent folder also selects every folder inside it.
Filters for automated test runs
Apply the following filters when Test run type is set to Automated:
| Filter | Details |
|---|---|
| Projects | The projects the test runs belong to. |
| Unique Run Name | A named test run. |
| Test run tags | The tags applied to the test runs. |
| Test tags | The tags applied to the tests. |
| Last executed by | The users who last updated the test result. One widget holds up to 30 users. |
| Hooks Visibility | Which hooks count toward the test count. See visibility of hooks and tests. |
| Host names | The hosts that ran the tests. |
| Folder names | The folders in your test repository. Use it to identify modules. |
| Include muted tests | Whether muted tests count toward the chart. |
| Include re-run attempts | Whether re-run attempts count toward the chart. |
| CI runs only | Only the runs a CI pipeline triggered. |
| Branch | The code branch the tests ran against. |
| Device | The devices the tests ran on. |
| OS | The operating systems the tests ran on. |
| Browser | The browsers the tests ran on. |
Drill down for more information
The chart answers who holds the work. To find which projects and runs that work sits in, open the breakdown for one segment:
- Hover over a bar segment.
- Select View breakdown in the tooltip.

The Test Execution Distribution Drilldown panel opens a project-wise breakdown of the segment you selected. The top of the panel repeats the row label, the execution count, and the status.
Under Projects, each project shows its matching test count. Expand a project to list its test runs, each with its own matching test count. Select View tests on a run to open that run in a new tab, with the status filter already applied.
Interpreting test data
The following patterns come up most often in the chart:
| Pattern | Likely cause | Action |
|---|---|---|
A long Untested segment late in a cycle. |
The assigned executions have not started. | Check availability with the owner, or reassign the test cases. |
| One bar much longer than the rest. | Execution work sits with a single user. | Spread assignment across more users, so no one person blocks sign-off. |
| A folder with almost no executions. | The module is not covered by the current runs. | Confirm whether the module is in scope, then add its test cases to a run. |
Next steps
To keep building your dashboard, read the following pages:
- Test Management-specific dashboard widgets
- Active test runs widget
- Statistics cards widget
- Test Execution Distribution widget in Test Reporting & Analytics
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!