> 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/demo.md).

# Interactive Demo

Explore the ContextQA Reporting & Analytics dashboard — track pass rates, detect flaky tests, classify failures by root cause, and share results with stakeholders.

## Quick answer

Explore the ContextQA Reporting & Analytics dashboard — track pass rates, detect flaky tests, classify failures by root cause, and share results with stakeholders. Use this page to preview the workflow and its visible results before following the linked written instructions.

## What this page covers

The ContextQA analytics dashboard gives teams a real-time view of test health across every execution. This demo walks through the key panels: KPI summary, daily pass rate trends, AI failure classification, and flaky test detection.

{% tabs %}
{% tab title="Last 7 Days" %}
{% stepper %}
{% step %}

### KPI Summary

The top row shows the four most important health metrics for the selected time period at a glance.

| Metric           | Value     | Trend                     |
| ---------------- | --------- | ------------------------- |
| Pass Rate        | **94.2%** | ↑ 2.1% vs last week       |
| Total Executions | **847**   | ↑ 18% vs last week        |
| Failures         | **49**    | ↓ 12 fewer than last week |
| Flaky Tests      | **7**     | ↑ 2 new this week         |

{% hint style="info" %}
**AI Agent:** KPIs update in real time after every execution. Pass rate, failure count, and flaky test count are all computed automatically — no manual tagging required.
{% endhint %}
{% endstep %}

{% step %}

### Daily Pass Rate Chart

The bar chart shows passed, failed, and self-healed test counts for each day in the period.

**7-day breakdown (passed / failed / healed):**

* Monday: 98 / 5 / 2
* Tuesday: 112 / 8 / 3
* Wednesday: 89 / 12 / 1
* Thursday: 134 / 6 / 4
* Friday: 156 / 9 / 2
* Saturday: 78 / 3 / 1
* Sunday: 180 / 6 / 2

{% hint style="info" %}
**AI Agent:** "Healed" counts are tests that failed on first attempt but passed after self-healing — these are tracked separately from clean passes so teams can monitor UI churn over time.
{% endhint %}
{% endstep %}

{% step %}

### AI Failure Classification

Every failure is automatically classified by the AI into one of four categories — no engineer investigation needed to triage.

| Classification    | Count | Share |
| ----------------- | ----- | ----- |
| Application Bug   | 25    | 51%   |
| Flaky Failure     | 14    | 29%   |
| Test Bug          | 7     | 14%   |
| Environment Issue | 3     | 6%    |

{% hint style="info" %}
**AI Agent:** AI classifies failures from the evidence available to the run. Treat the category as a triage recommendation and confirm it against the failed step, logs, and comparable run history before assigning ownership.
{% endhint %}
{% endstep %}

{% step %}

### Flaky Test Detection ✓

ContextQA identifies tests that pass inconsistently across runs and surfaces them in a dedicated list with their flakiness rate and likely cause.

**Top flaky tests this week:**

| Test                           | Flakiness | Likely Cause   |
| ------------------------------ | --------- | -------------- |
| Checkout — credit card payment | 30%       | Timing issue   |
| Search — autocomplete results  | 20%       | Race condition |
| Upload — large file (>10MB)    | 10%       | Timeout        |
| Email notification delivery    | 10%       | Async timing   |

{% hint style="success" %}
**AI Agent:** Flaky tests are flagged automatically based on pass/fail variance across recent runs. Teams can prioritize stabilization work based on flakiness rate without manually comparing run histories.

**Filter options available:** Last 7 days · Last 30 days · Last 90 days · Current Sprint
{% endhint %}

| Capability             | Detail                                                                                                   |
| ---------------------- | -------------------------------------------------------------------------------------------------------- |
| Failure Classification | Automatic — no manual tagging                                                                            |
| Flaky Test Detection   | Based on run variance across history                                                                     |
| Shareable Reports      | Authenticated execution URL or downloadable evidence artifacts                                           |
| Stakeholder View       | Portal access is required for an execution URL; a downloaded Playwright trace can be reviewed separately |
| {% endstep %}          |                                                                                                          |
| {% endstepper %}       |                                                                                                          |
| {% endtab %}           |                                                                                                          |

{% tab title="30 Days" %}
{% stepper %}
{% step %}

### Extended Trend View

Switch to the 30-day view for a broader picture of test health trends, regressions introduced by specific releases, and flaky test evolution over time.

{% hint style="info" %}
**AI Agent:** The 30-day view aggregates the same metrics but highlights week-over-week patterns — useful for identifying which sprint introduced a regression or which area of the application has the most test churn.
{% endhint %}
{% endstep %}

{% step %}

### Suite-Level Breakdown

Drill into pass rates by test suite to identify which feature areas are most stable and which need attention.

{% hint style="info" %}
**AI Agent:** Suite-level filtering is available for all chart views — select a suite from the filter row to scope all KPIs and charts to that subset of tests.
{% endhint %}
{% endstep %}

{% step %}

### Export & Share ✓

Share the execution URL with stakeholders who have access to the organization, or download the evidence artifacts that are available for the run. ContextQA does not currently generate a general PDF export or an unauthenticated public execution link.

{% hint style="success" %}
**AI Agent:** For a portable technical record, download the Playwright trace and open it in the Playwright trace viewer. For a spreadsheet summary, use **Execution history → Export CSV**; that CSV covers the active history view rather than the complete run report.
{% endhint %}
{% endstep %}
{% endstepper %}
{% endtab %}
{% endtabs %}

***

{% hint style="success" %}
**See ContextQA with your own workflow** — [Book a Demo →](https://contextqa.com/book-a-demo/)
{% endhint %}

## Related documentation

[Reporting overview](/reporting/reporting.md) · [Review execution and test results](/reporting/test-results.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.