> For the complete documentation index, see [llms.txt](https://learning.contextqa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learning.contextqa.com/reporting.md).

# Reporting

- [Reporting Overview](https://learning.contextqa.com/reporting/reporting.md): An overview of the dashboards, reports, and analytics that ContextQA provides to help QA teams, developers, and engineering managers understand test health at every level.
- [Test Results](https://learning.contextqa.com/reporting/test-results.md): Monitor a ContextQA test, inspect results and evidence, identify the mobile app build used by a run, and download a retained build for reproduction.
- [Execution History](https://learning.contextqa.com/reporting/execution-history.md): Compare a test plan's recent runs side by side with ContextQA's execution history — a per-run matrix, plan summary, pass-rate trends, and CSV export.
- [Analytics Dashboard](https://learning.contextqa.com/reporting/analytics-dashboard.md): A guide to the dashboards and analytics surfaces in ContextQA, including execution trends, coverage, AI insights, and risk-based testing.
- [Failure Analysis](https://learning.contextqa.com/reporting/failure-analysis.md): Review failed-test evidence, distinguish observed defects from blocked runs, assess root-cause hypotheses, and prepare a reproducible engineering handoff.
- [How to Debug a Failing Test](https://learning.contextqa.com/reporting/debugging-failing-tests.md): A step-by-step workflow for diagnosing why a test failed using ContextQA's execution evidence — AI root cause analysis, screenshots, video, network logs, console logs, and Playwright traces.
- [Find and Fix Flaky Tests in CI](https://learning.contextqa.com/reporting/flaky-test-detection.md): Diagnose flaky CI tests with repeatable Playwright runs, isolated state, and first-failure evidence, then use ContextQA to investigate managed test results.
- [Exporting Reports](https://learning.contextqa.com/reporting/exporting-reports.md): Test report export from ContextQA — share execution URLs, download evidence packages, export Playwright code, and embed results in Jira and Slack notifications.
- [Interactive Demo](https://learning.contextqa.com/reporting/demo.md): Explore the ContextQA Reporting & Analytics dashboard — track pass rates, detect flaky tests, classify failures by root cause, and share results with stakeholders.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learning.contextqa.com/reporting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.