Reporting Overview
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.
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.
Quick answer
ContextQA reporting combines a workspace overview, execution health, test results, coverage signals, failure analysis, and risk views. Testers use result evidence to debug a run; QA managers use activity, drafts, trends, and consistently failing tests to manage suite health; engineering leaders use scoped readiness and risk signals to support release decisions. A dashboard is decision support, not a replacement for reviewing the underlying execution or pull-request evidence.
Who uses reporting in ContextQA?
QA engineer
Did my last run pass? What failed and why?
Execution Dashboard → test run detail
QA manager
What needs review, and what is our pass rate, flakiness, and coverage trend?
Dashboard → Review drafts or 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
Workspace overview dashboard
The Dashboard is the workspace starting point. Depending on workspace availability, it can show:
summary cards for test cases and recorded bugs;
estimated time and cost saved;
regressions caught and pull requests checked;
connected integrations;
module or coverage status;
recent test, requirement, and pull-request activity;
a Finish setup checklist;
a workspace standing or trial banner; and
a live activity terminal while setup or analysis is running.
A Review drafts card appears only when PR Impact has draft recommendations waiting for review. Its count is a work queue, not a release verdict. Open the drafts and inspect the associated pull request, recommendation, confidence, and evidence before taking action.
Treat estimated savings and coverage values as directional unless your organization has validated the inputs and definition. Use the linked test, requirement, pull request, execution, or usage record for an auditable decision.
Execution analytics dashboard
The execution analytics view summarizes activity and run health over a selected period. Use the date range and available plan filters to scope the view to a sprint or release window before comparing trends.
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 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.
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 — understanding execution result pages
Analytics Dashboard — dashboards, trends, and AI insights
Failure Analysis — root cause analysis, flakiness, and bug tracker integration
Execution Evidence
The following recording is from a live ContextQA execution of the analytics dashboard:
FAQs
Last updated
Was this helpful?