> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/dashboard/tests/test-history.md).

# Test History

Explore historical Playwright and Cypress tests performance with Test History

### Test History overview

Test History helps you review the historical performance of individual tests across different runs and branches. You can view this data as a chart or a list, and merge or pin branches.

{% embed url="<https://player.mux.com/Nkr100jOgrd1hCuml71jghMb4VK02Y6mXCFMixHDFldHc?min-resolution=1080p>" %}
Test History View
{% endembed %}

Each individual bar represents an instance of the test. The bars are arranged in chronological order.\
Hovering over a bar displays the run’s details, and clicking on a bar opens the recorded test instance with full information.

The bars are colored as follows:

* <mark style="color:red;">red</mark> - failed
* <mark style="color:green;">green</mark> - passed
* <mark style="color:purple;">purple</mark> - passed but flaky
* grey - test was ignored
* <mark style="color:orange;">orange</mark> - test was skipped due to a failure

### How to access Test History?

You can access the Test History in two ways:

1. Through the **History** tab in the [Test View](/dashboard/tests/test-view.md).
2. Through the **History** section of the [Test Explorer](/dashboard/test-suite-performance-explorer/tests-explorer.md).

### Test History Controls

#### Time Range Filter

Filter test executions by a specific time range: 7, 14, 28, or 45 days.

#### Test State

Filter test executions by [Test Status](/dashboard/tests/test-status.md).

#### Merge Branches

Toggle **Merge Branches** to display a consolidated timeline across all branches.

#### Pin Branch

Show timelines only for selected branches.

{% hint style="info" %}
Please note: only branches detected within the fetched test instances will show up.
{% endhint %}

### FAQ

#### What instances represent the same test across different runs?

Instances with the same spec file, project and title will be considered as belonging to the same test - i.e. renaming a test or renaming a spec file will "detach" it from its history.


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.currents.dev/dashboard/tests/test-history.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.