Ask the Community
Statistics cards
Show a single headline metric on your dashboard, as a count or percentage of your test cases or defects.
The statistics cards widget shows one headline number on your dashboard. It counts test cases or defects. The card shows that number as a count or as a percentage. Use it to anchor a dashboard with a headline total, such as the count of active test cases.
This widget counts test cases or defects, not test executions, runs, or builds.
How values are calculated
The See values in control switches the card between two modes. In Number mode, the card shows a count of the records that match your filters. In Percentage mode, the card shows those records as a share of a fixed total.
The numerator and denominator of the percentage are scoped differently. The numerator is the number of records that match your filters.
Filters such as automation status, folder, priority, type, owner, tags, and custom fields change only the numerator. The denominator always counts all active test cases in the selected projects.
Widget configuration
You can configure the following options in the statistics cards widget:
-
Entity Type sets what the card counts:
- Test Cases, the default, counts records in your test case repository.
- Defects counts records in your defects list.
- See values in sets the display mode. Choose Number for a count or Percentage for a share.
- Filters narrow which records the card counts.
The following filters are available:
| Filter | What it narrows by |
|---|---|
| Projects | The projects the test cases belong to. |
| Folders | The folders that hold the test cases. |
| Test Case Tags | The tags applied to the test cases. |
| Priority | The priority levels. |
| Owner | The owning users. |
| State | The lifecycle state, such as Active, Draft, or Deprecated. |
| Automation Status | Whether cases are automated or not automated. |
| Type of Test Case | The type, such as Functional or API. |
Use cases and actionable insights
Use the card to spot issues in your test suite or defect backlog and act on them:
| Insight | Action |
|---|---|
| A low share of automated test cases | Prioritize high-value manual cases for automation. |
| A high count of open defects | Assign owners and plan triage. |
| A high share of priority-1 test cases | Review whether the prioritization still reflects current risk. |
Interpreting test data
- Increasing failure counts suggest recent problematic code changes.
- Stable pass rates indicate reliable test practices.
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!