> 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/execution-history.md). # Execution History {% hint style="info" %} **Who is this for?** QA managers, SDETs, and testers who want to see how a test plan has performed across its recent runs — which test cases keep failing, how the pass rate is trending, and where stability is improving or regressing. {% endhint %} A single run tells you whether a plan passed or failed today. **Execution history** tells you the story across many runs: it lines up a test plan's most recent executions side by side so you can spot recurring failures, flaky test cases, and pass-rate trends over time. *** ## Opening execution history You can open execution history from two places. ### From a test plan 1. Navigate to **Test Development** → **Test Plans** in the left sidebar. 2. Click a plan to open its detail page. 3. Click the **Execution History** tab. The tab loads the history for that plan only. ### From the dashboard 1. Open the execution dashboard for a plan run. 2. Use the **Analytics** / **Execution History** toggle at the top of the view to switch to **Execution History**. 3. Select a plan from the plan dropdown to load its runs. *** ## Reading the report The execution history view has three parts: a control bar, a row of summary cards, and a report table. ### Summary cards A row of summary cards sits above the table and aggregates the executions currently in view: * **Passed** — number of test case results that passed. * **Failed** — number that failed. * **Aborted** — number that aborted mid-run. * **Skipped** — number skipped due to unmet prerequisites or configuration. * **Total** — total test case results across the runs shown. * **Pass rate** — passed results as a percentage of the total. Below the cards, a row of meta chips shows the number of test cases, how many executions appear, the date range covered, and the plan ID. ### Test case matrix The **Test case matrix** view answers "which test cases keep failing?" Each row is a test case and each column is one plan run, ordered with the most recent run first. Every cell shows a status badge for that test case in that run: | Badge | Meaning | | ----------- | -------------------------------------------------- | | **Passed** | The test case passed in that run. | | **Failed** | The test case failed in that run. | | **Aborted** | The run was aborted before the test case finished. | | **Skipped** | The test case did not run in that execution. | Each row also shows the test case's pass rate across the runs in view, so a test case that fails intermittently stands out from one that fails every time. ### Plan summary The **Plan summary** view answers "how did each run do overall?" Each column is a run and each row is a status category (Passed, Failed, Aborted, Skipped, and Total), with the count of test cases in that category for the run. Use this view to see pass and fail counts trend from one run to the next. Switch between the two views with the report toggle in the control bar. *** ## Controls The control bar at the top of the view provides: | Control | What it does | | ------------------- | ----------------------------------------------------------------------------------------------------------------- | | **Report toggle** | Switches between the **Test case matrix** and **Plan summary** views. | | **Plan dropdown** | Selects which plan to show. Hidden when you open the tab from a specific plan, which locks the view to that plan. | | **Execution limit** | Sets how many recent runs to include: **Last 10**, **Last 30**, or **Last 50 executions**. | | **Export CSV** | Downloads the data in the active view as a CSV file. | *** ## Exporting to CSV Click **Export CSV** to download the report. The export matches the view you are looking at: * From the **Test case matrix** view, the CSV has one row per test case and one column per run. * From the **Plan summary** view, the CSV has one row per status category and one column per run. Use the export to share results with stakeholders or to track pass-rate trends in your own spreadsheets. *** ## Empty state If the selected plan has no recorded executions, the view shows an empty state instead of a table. Run the plan at least once — see [Running tests](/execution/running-tests.md) — and the run appears in execution history once it completes. *** ## Related pages * [Test plans](/web-testing/test-plans.md) * [Test results and reports](/reporting/test-results.md) * [Analytics dashboard](/reporting/analytics-dashboard.md) * [Flaky test detection](/reporting/flaky-test-detection.md) * [Running tests](/execution/running-tests.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/execution-history.md?ask=&goal= ``` `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.