> ## 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 a single test case across runs: pass and fail history, duration trend, and the reliability score derived from them.

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 reliability score, total runs, and outcome counts" />

### Test Metrics

Key metrics for this test on the active branch:

* **Reliability:** A score from 0 to 100, higher is better. It is not a percentage of runs that passed. See [Reliability score](#reliability-score).

* **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.

* **Incomplete:** Runs that ended without a result, usually because the test run was interrupted. It appears only when there are some, and it makes the outcome counts add up to Total Runs.

### 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" 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** | The test run this execution belongs to | Opens this test case as it ran in that test 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>

## Reliability score

Reliability scores a test from 0 to 100 on the current branch, higher is better. It combines how often the test passed, how rarely it was flaky, and whether retries recovered it. The score covers the entire tracked history, not only the most recent run.

| Score | Reading |
| :- | :- |
| 80 and above | Healthy |
| 50 to 79 | Shaky |
| Below 50 | Unreliable |

Because it weighs flakiness and recovery alongside passes, a test that passes most runs but flakes often scores lower than its pass count suggests. The Overview tab shows the same score under the same name.

## 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>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.