# Reporting Overview
{% hint style="info" %}
**Who is this for?** QA managers, engineering managers, and VPs who need clear visibility into test health, pass rates, flakiness trends, and release readiness — without manual spreadsheet tracking.
{% endhint %}
ContextQA centralizes all test quality data into a set of dashboards and reports so every stakeholder has the right view of what is happening across the test suite. From a real-time execution feed to AI-generated quality observations, the reporting layer surfaces the information you need without requiring manual spreadsheet tracking or log diving.
***
## Who uses reporting in ContextQA?
| Role | Primary concern | Recommended starting point |
| ----------------------------------- | -------------------------------------------------------------------------------------- | ---------------------------------------------- |
| **QA engineer** | Did my last run pass? What failed and why? | Execution Dashboard → test run detail |
| **QA manager** | What is our overall pass rate, flakiness, and coverage trend? | Dashboard → Execution Dashboard → Coverage tab |
| **Developer** | Which specific step failed, what did the UI look like, and what is the fix suggestion? | Test result detail page → Failure Analysis |
| **Engineering manager / executive** | Are we shipping with confidence? How is quality trending across sprints? | Dashboard → Insight tab → RBT tab |
***
## What is available
### Main Dashboard
The **Dashboard** (accessible from the left sidebar) is your command center. It shows:
* Total test case volume split by web, mobile, and API
* Daily activity trend comparing AI-driven actions (auto-heal, root cause analysis) versus human interventions
* A daily bar chart breaking down cases created, reviewed, executed, root-cause-identified, and auto-healed
Use the date range picker to scope all widgets to a sprint or release window. Toggle between line and bar chart modes on the activity trend widget.
### Execution Dashboard
The **Execution Dashboard** gives a live and historical view of every test run. Key panels include:
* Run-level summary: total executed, passed, failed, aborted, and success rate versus previous period
* Execution trend graph: daily pass/fail/aborted counts over time
* Test distribution widget: environment breakdown (web, mobile, API)
* Consistently failing test cases: a ranked list with root cause and failure count per case
### Coverage Dashboard
The **Coverage** tab inside the Execution Dashboard shows which application modules have test coverage and which do not. Each module card lists positive, negative, and ad-hoc scenarios and flags unresolved issues with a red badge.
### Insight and Risk-Based Testing
The **Insight** tab surfaces test health and readiness blockers — missing test data, broken prerequisites — with priority, source, and status for each blocker. The **RBT (Risk-Based Testing)** tab provides a heatmap matrix mapping test cases and defects against business priority and usage frequency so you can direct effort toward the highest-risk areas.
### Test Result Detail Pages
Each individual test execution has a detail page showing step-by-step pass/fail results, screenshots, video replay, and downloadable Playwright trace files. See [Test Results](/reporting/test-results.md) for a full walkthrough.
### Failure Analysis
The failure analysis view provides AI-generated root cause explanations, fix suggestions, and flaky test detection. Failures can be pushed directly to Jira or Azure DevOps. See [Failure Analysis](/reporting/failure-analysis.md).
***
## Navigating to reports
All reporting surfaces are reachable from the **left sidebar**:
* **Dashboard** — top-level platform summary
* **Execution Dashboard** — run history and per-run detail
* **Reports** — detailed pass/fail reports with screenshots, video, and step logs
***
## In this section
* [Test Results](/reporting/test-results.md) — understanding execution result pages
* [Analytics Dashboard](/reporting/analytics-dashboard.md) — dashboards, trends, and AI insights
* [Failure Analysis](/reporting/failure-analysis.md) — root cause analysis, flakiness, and bug tracker integration
***
## Execution Evidence
The following recording is from a live ContextQA execution of the analytics dashboard:
***
## FAQs
How do I scope dashboard data to a specific sprint or date range?
Use the date range picker at the top-right of the Dashboard page to filter all widgets to a specific window. You can select a preset (last 7 days, last 30 days) or define a custom range.
Can I export test results for stakeholder reporting?
Yes. See [Exporting Reports](/reporting/exporting-reports.md) for instructions on downloading results as PDF or CSV, and for sharing report links with stakeholders who don't have a ContextQA login.
Where do I see which tests are consistently flaky?
The Execution Dashboard's **Consistently failing test cases** panel ranks tests by failure count. The [Failure Analysis](/reporting/failure-analysis.md) view provides AI-generated root cause explanations and flaky test detection across your suite.
{% hint style="info" %}
**Get release readiness reports your stakeholders understand** [**Book a Demo →**](https://contextqa.com/book-a-demo/)
{% endhint %}
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://learning.contextqa.com/reporting/reporting.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.