> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testdino.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Playwright Test Case History Tracking

> Track stability and execution history for a single test case.

The History tab shows every execution of a single test case on the active branch. Use it to measure stability over time and confirm whether failures are new, recurring, or flaky.

<Note>
  **Note**

  Only runs from the active branch appear. Test runs from other branches are excluded.
</Note>

## Metrics & History

<img src="https://tdstorageus.blob.core.windows.net/public/docs/debug-and-analyze/test-case-results/playwright-test-case-history/kpi-tiles.webp" alt="Test case history KPI tiles showing stability percentage, total runs, and outcome counts" />

### Test Metrics

Key metrics for this test on the active branch:

* **Stability:** Percentage of runs that pass. A 100% stability score means the test passed in all tracked executions.

  Stability is calculated as `(Passed Runs ÷ Total Runs) × 100`

* **Total Runs:** The total number of executions tracked on this branch. Provides context for all other metrics.

* **Passed / Failed / Flaky / Skipped:** Counts for each outcome.

### Last Status Tiles

Links to the most recent run for each outcome: **Last Passed**, **Last Failed**, **Last Flaky**.

Each tile shows the **Run #** and timestamp. The **current** label appears when the tile matches the run you are viewing.

### Execution History Table

<video controls loop preload="metadata" aria-label="Execution history table showing test runs with status, duration, retries, and expandable error details" poster="https://tdstorageus.blob.core.windows.net/public/docs/debug-and-analyze/test-case-results/playwright-test-case-history/execution-histroy-table-poster.jpg" src="https://tdstorageus.blob.core.windows.net/public/docs/debug-and-analyze/test-case-results/playwright-test-case-history/execution-histroy-table.mp4" />

Lists every execution on this branch in time order.

| Column           | Description                             | Why it matters                                  |
| ---------------- | --------------------------------------- | ----------------------------------------------- |
| **Executed at**  | Timestamp when the test ran             | Correlates failures with commits or deployments |
| **Run**          | Unique identifier for the test run      | Navigate to the exact run                       |
| **Status**       | Outcome: Passed, Failed, Flaky, Skipped | Spot trends and recurring issues                |
| **Duration**     | Total runtime of the execution          | Identify performance regressions                |
| **Retries**      | Number of retry attempts                | Surfaces flaky or unstable tests                |
| **Run location** | Link to the CI job                      | Access to the original build and logs           |
| **Actions**      | Link to execution details               | Inspect evidence and artifacts                  |

<Note>
  **Note**

  Rows expand to show **Error Details** for failures or **Console Logs** if they were captured during execution.
</Note>

## Stability Score

Stability measures a test's reliability on the current branch. The percentage reflects the entire history, not only the most recent run.

* **100% Stability:** Test passes in every tracked run on this branch.
* **\< 100% Stability:** At least one run failed or was flaky, even if the latest run passed.

## Related

<CardGroup cols={2}>
  <Card title="Overview" icon="book-open" href="/platform/playwright-test-cases">
    Test case status and evidence
  </Card>

  <Card title="Test Runs" icon="play" href="/platform/playwright-test-runs">
    View all test executions
  </Card>
</CardGroup>