> 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

### Test History overview

Test History helps you to review the historical performance of individual tests across different runs and branches.

{% embed url="<https://www.loom.com/share/fea3d6bfdf654fd8b3db8522f9c2354d?hideEmbedTopBar=true>" %}

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:blue;">blue</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).

#### Collapse Branches

Toggle "Collapse Branches" to show/collapse timelines for individual branches for more effective troubleshooting.

#### 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 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://docs.currents.dev/dashboard/tests/test-history.md?ask=<question>&goal=<endgoal>
```

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