Skip to main content
No Result Found
Get your setup working faster. Join our Discord for optimisation tips from elite testers. Join our DiscordJoin our Discord

Test Executions widget in custom dashboards

Track how many automated tests you run over time, and compare the trend across teams, modules, and platforms.

The Test Executions widget is a line chart of test execution counts over time. It counts every execution, not unique test cases, so a test that ran ten times adds ten to the count. Use it to check whether your automation volume is growing, and to compare teams, modules, or platforms on one chart.

Test Reporting & Analytics reports automated test runs only. To track manual execution volume, use the test executions widget on a Test Management dashboard.

The Test Executions widget on a dashboard, with a tooltip showing one period's execution count and the View breakdown link.

Summary of widget data and visualization

Each line on the chart is one segment. A segment is a named set of filters, such as one team’s projects or one platform. The legend names each segment and gives it a color. The widget gallery lists this widget as Tests Executions.

The X-axis follows the dashboard date range, so the range you pick sets how much time each point covers. A 7D range plots one point per day. A wider range, such as 3M, groups executions into weeks, so a single point covers a longer period.

Key metric information and visualization

The following table describes each element of the chart:

Element Details
Total The execution count for the whole dashboard date range. It appears above the chart when Show chart summary is on and the widget has one segment.
Legend Names each segment and gives it a color.
Point One time period. Hover over a point to read the start and end of the period in your time zone, the segment name, and its execution count.
View breakdown Appears in the tooltip on the dashboard. Opens the project-wise breakdown for that point.
Info icon Shows the widget description next to the widget title. When you have not added a description, it shows the default text Observe the trend of total tests executed over time.

Add the widget

Follow these steps to add the widget to a custom dashboard:

  1. Open a dashboard and select Tests Executions from the widget gallery. The widget dialog opens with a live preview.

    The Add Widget gallery filtered to the search term Execution, showing the Tests Executions card.

  2. Enter a Widget name. To add a note for readers, click Add a description and enter up to 200 characters.
  3. Turn on the Show chart summary toggle to show the total count for the chart.
  4. Under Segments, enter a Segment name and add the filters for that line. Click Add segment for each extra line you want to compare.
  5. Check the preview, then click Save.

The widget dialog with a description, Show chart summary on, one segment with a Projects filter, and the live preview.

The following table describes each option in the widget dialog:

Option Details
Widget name Required. Defaults to Tests Executions. Names the widget on the dashboard.
Add a description Optional note of up to 200 characters. Readers see it on the info icon next to the widget title.
Show chart summary Shows the Total for the chart. On by default. Turns off when the widget has more than one segment.
Segment name Required for every segment. Labels the line in the legend.

Segments

Segments are how you compare teams, modules, or platforms inside a single widget. Each segment is one line on the chart, and each carries its own filters. Every segment needs a Segment name, because that name labels the line in the legend.

Use the following controls on a segment card:

  • Click Add segment to add a line.
  • Click the copy icon to duplicate a segment with its filters.
  • Click the delete icon to remove a segment. The icon appears only when the widget has more than one segment.

A widget holds up to five segments. From the second segment onwards, the widget warns that more segments can reduce the readability of the data, and Show chart summary turns off because the Total applies to a single line.

Available filters

Filters apply per segment, so two lines on the same chart can cover different data. No filter applies until you add one. To add a filter, click Add filter, select a field, then pick the values you want. After you add the first filter, Clear filters appears next to Filters. Click it to remove every filter on that segment.

Some filters have a match operator next to the filter name. It sets how the values you select combine. The default, Matches any one value (OR), counts an execution when it matches any selected value. When a filter also offers Matches all values (AND), that option counts an execution only when it matches every selected value.

A segment card with a Projects filter added, showing the match operator, the delete icon, Clear filters, and the open Add filter list.

To reuse a filter set from another widget on the same dashboard, click Import from other widgets. Apply the following filters to a segment:

Filter Details
Projects The projects the test runs belong to.
Unique Run Name A named test run.
Users The users who triggered the builds the tests belong to.
Last executed by The user who last set the test result. When someone updates a test result by hand, that user becomes its last executor.
Teams The teams of the users who triggered the builds.
Build tags The tags applied to the builds.
Test tags The tags applied to the tests.
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.
Failure Categories The failure categories assigned to the failed tests.

The list also carries a Custom fields group for the custom fields defined in your projects.

Users and Last executed by answer different questions. Users counts the tests in the builds that the selected users triggered. Last executed by counts the tests whose current result those users set last. The user who triggered the build is the last executor until someone updates that test’s result by hand.

A segment in the Tests Executions widget dialog with the Last executed by filter added and one user selected.

Drill down for more information

The chart tells you how many tests ran. The breakdown pane tells you which projects those executions belong to. Follow these steps:

  1. On the dashboard, hover over a point on the chart.
  2. Click View breakdown. The Tests Executions Drilldown pane opens.
  3. Read the segment name, the execution count, and the period at the top of the pane.
  4. Read the Project table. Each row is one project with its execution count for that period, sorted from the highest count down.
  5. Click View tests next to a project. Tests Health for that project opens in a new tab, filtered to the same period.

The Tests Executions Drilldown pane listing each project's execution count for the selected period, with a View tests link on every row.

Interpreting test data

A rising line can mean wider coverage. It can also mean the same tests running more often. Use the following patterns to tell the two apart:

Pattern Likely cause Action
A drop to near zero across one or more points Almost nothing reported in that period, such as a paused pipeline or a release freeze Hover over the low point, click View breakdown, and check which projects stopped reporting.
One segment flat at zero while the others move The segment’s filters match no executions Open the segment and widen or clear its filters.
A single tall spike A full-suite run or a batch of re-run attempts landed in one point Drill into the spike and compare its project counts against a normal point.
Volume rising while your test case count stays flat The same tests running more often, so coverage has not grown Read the Unique Test Cases widget before you report coverage growth.
A step change on the day a project was added A new project started reporting into the dashboard scope Add a Projects filter to hold the segment to a fixed set of projects.

Next steps

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

Is this page helping you?

Yes
No

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!

Talk to an Expert
Download Copy Check Circle