The Analytics tab gives you a live dashboard of your project's testing activity. All metrics and charts update in real time based on the filters you apply.
The Analytics tab is available to Admin and Member roles only.
1. Open Analytics
Open a project and click the Analytics tab in the left-hand navigation.
2. Key metrics
Four metric cards appear at the top of the page. Each one reflects the current filter selection.
Total Test Cases: the number of test cases in the project.
Reported Bugs: the number of bugs filed against test runs through a connected bug-tracker integration (Jira, Linear, Azure DevOps, ClickUp, Shortcut, or Notion). If no integration is configured, the card shows No integrations connected. Hover it for a short explanation.
Total Test Runs: the total number of test runs executed within the selected period.
Pass Rate: the percentage of test runs that passed, calculated across the selected period.
Reported Bugs requires at least one bug-tracker integration to be active on your project. Connect one from your project's Integrations settings to start tracking reported bugs.
ROI / Estimated time saved
Below the metric cards, the ROI / Estimated time saved band estimates the hours that Thunders saved your team in the selected period. It shows two figures. Do not add them together, because each one compares Thunders with a different way of working.
Compared with manual testing: the time that a person would spend to run every test by hand. It counts the test executions and the bugs found.
Compared with scripted automation: the time that your team would spend to keep these tests in code. A machine runs scripted tests either way, so it counts only the steps that Thunders repaired and the bugs found. Below this figure, a line gives the share of elements that changed and the share of them that Thunders repaired. These rates count only the steps where Thunders had already saved how to find the element.
A line under each figure gives the counts behind it. The bugs found are the Reported Bugs, so they count only when a bug-tracker integration is connected.
Thunders cannot measure the minutes that each task saves, so you set them. Click Minutes per task to open the Minutes saved per task panel:
Task | Default |
A test execution | 12 min |
A step repaired | 30 min |
A bug found | 20 min |
Your browser keeps the values that you set, and they apply only to you. The button shows how many values you changed. Click Reset to the Thunders defaults to go back to the defaults.
3. Filter the data
The filter bar sits at the top of the page, above the metric cards. Adjusting any filter instantly updates the metric cards and all charts on the page.
Filter | What it does |
Date | Restrict runs to a date range. Pick a preset (Today, Yesterday, Last 7 days, Last 30 days, Last 90 days, Last week, Last month) or set a custom From / To date. Defaults to the last 30 days. |
Execution Mode | Show only runs triggered manually from the app (App), runs triggered via CI/CD (CI), or both (All). |
Test Sets | Limit results to one or more specific test sets. |
Environment | Limit results to one or more environments. |
Labels | Limit results to test cases that carry specific labels. |
Created By | Show only runs initiated by a specific team member. |
Click Reset to clear all active filters at once.
Filters are stored in the URL. Bookmark or share a filtered view and it opens with the same filters applied.
4. Charts
Test Runs Over Time
A stacked bar chart showing the daily volume of test runs, broken down into Passed and Failed counts. Use it to spot trends: a spike in failed runs on a given day is a fast signal to investigate what changed.
Pass Rate Over Time
An area chart tracking your overall pass rate day by day. A dashed reference line marks the 50% threshold at a glance. Gaps in the line indicate days with no test activity.
Test Runs by Status
A donut chart showing the overall distribution of run results across three categories: Success, Failed, and Other (cancelled, skipped, or runs still in progress). Hover a slice to see the exact count.
Test Runs by Browser
A donut chart breaking down runs by the browser or device used during execution (Chrome, Firefox, Safari, Edge, Chromium). Use it to check cross-browser coverage and quickly spot whether failures are concentrated on a specific browser.
Test Runs by Persona
A donut chart grouping runs by the persona used during execution. Use it to verify that critical user journeys are being covered across all your configured personas.
5. Empty states
When no runs match the active filters, charts and metric cards display an empty state with the message No runs match these filters. Try widening the date range or clicking Reset to clear filters.
If the project has never had a test run, a full-page empty state appears instead. Execute your first test to start populating Analytics.
