Join our Discord
Use Reports in Test Reporting & Analytics
Learn what reports are in Test Reporting & Analytics, the two report types available, and how reports differ from dashboards.
A report is a structured, configurable artifact that you can export, share, and archive. You create a report by selecting data sources such as projects, builds, tags, and metadata. You then choose table columns and add stat tiles such as flaky tests, new failures, always failing, and open issues.
After you create a report, you can view it with your own filters, drill down, export, and share it without changing the saved definition. A report stays fixed until you edit it.
Report types
Test Reporting & Analytics supports the following report types:
- Build Comparison Reports to diff two specific builds.
-
Test Execution Reports to know the overall state across many builds.
Difference between dashboards and reports
The following table summarizes the key differences between dashboards and reports in Test Reporting & Analytics:
| Feature | Dashboards (Dynamic Monitoring) | Reports (Authoritative Snapshots) |
|---|---|---|
| Primary Purpose | Real-time, iterative monitoring during active development and CI cycles. | Point-in-time, formal artifacts for audits, approvals, milestone reviews, and coverage evidence. |
| Format & Display | Primarily chart/graph widgets (time-series, live trend visualization). | Primarily tabular data with a focused set of stat tiles and limited charts. |
| Interaction | Highly customizable layouts and on-the-fly experimentation. | Defined once in Edit Mode; View Mode prevents accidental structural changes. |
| Versioning | Not versioned; always reflects the most current, live data. | Planned support for snapshots (multiple versions annotated, for example, “Release v13”). |
| Distribution | Mostly in-platform usage by active team members. | Designed for export (PDF, CSV), sharing (public/private link), and archival. |
| Workflow Fit | Continuous observation, triage, and quick pivoting. | Sprint completion, release readiness, compliance, and historical comparison. |
| Strategic Principles | Use dashboards for dynamic monitoring; focus on real-time insights. | Use reports for authoritative snapshots; focus on formal documentation. |
Related resources
Reports and Dashboards together provide a comprehensive view of your testing landscape. Check out the custom dashboards documentation to understand whether a report or a dashboard is the better fit for your use case.
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!