> 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/~/changes/TYKBeqcc7WyqjmgOzWzB/dashboard/tests/test-history.md).
# Test History
Explore historical Playwright and Cypress tests performance with Test History snipper
### Test History Snipper overview
Test History helps you to review the historical performance of individual tests across different runs and branches.
Each individual dot is an instance of the test. The dots are arranged in chronological order.
Hovering over a dot will show individual run details. Clicking on a dot will open the recorded test instance and reveal its details.
The dots are coloured as follows:
* red - failed
* blue - passed
* purple - passed but flaky
* grey - test was ignored
* orange - test was skipped due to a failure
### How to access Test History Snippet?
* While browsing the tests list, click the "Test History" button, this will open the Test History Snippet in Preview mode:
* While browsing Test Details view, the full Test History Snippet is shown at the top of the view.
### Test History Snippet Controls
#### Show Items
Set the number of test instances to fetch - that includes past and future runs, we'll try to fetch an equal number of future and past instances.
{% hint style="info" %}
**Please note:** "Show Items" control is hidden for Preview mode and shows only 10 items.
{% endhint %}
#### Collapse Branches
Toggle "Collapse Branches" to show/collapse timelines for individual branches for more effective troubleshooting.
#### Branch Filter
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/~/changes/TYKBeqcc7WyqjmgOzWzB/dashboard/tests/test-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.