> 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/test-suite-performance-explorer/reference.md).

# Reference

How to read and use Test Explorer and Spec Files Explorer performance charts

## Performance Charts

Upon selecting the dates period, the charts show two lines:

* The primary <mark style="color:blue;">blue</mark> line shows the metric values for the selected period.
* The secondary \[gray] line shows the metric value for the period preceding the selected period.

For example, selecting a 14-day period reveals this type of chart:

<div data-with-frame="true"><figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2FHOfjgTVrGH0QO7LNMlNJ%2FScreenshot%202026-09-21%20at%2012.02.29.png?alt=media&amp;token=86485a98-4901-4c5b-a29b-7e441d1a6d93" alt=""><figcaption><p>Average Duration Chart</p></figcaption></figure></div>

* The blue line shows the metric value for the selected date range (last 14 days).
* The gray line shows the metric value for the previous date range (28 days ago to 14 days ago).
* The trend change value of <mark style="color:green;">**-6.67%**</mark> indicates that the metric value improved during the recent period compared to the preceding period.

Hovering over a particular day would reveal the change value compared to the preceding period for each metric:

{% embed url="<https://player.mux.com/GB02IGZFr2rUhvQQ4tCFKx71kN6HcoNPlo00PH02yOMu2c?min-resolution=1080p>" %}
Comparing performance for a specific date
{% endembed %}

Another example is the spec file analyzed in the image below. During the analysis, the peak of the **average duration** for this spec file occurred on the same day as the highest **failure rate** within the selected period.

<div data-with-frame="true"><figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2FLbkJJ3zzvFFRfQuaY8uV%2FScreenshot%202026-09-21%20at%2012.37.49.png?alt=media&amp;token=cc1b53dc-82a8-48dd-82a5-6aed39b19ac6" alt=""><figcaption><p>Peak of average duration and failure rate</p></figcaption></figure></div>

It suggests a potential correlation between the duration of the spec file's executions and its failure rate. The fact that the highest average duration aligns with the highest failure rate indicates that longer execution times may be associated with an increased likelihood of failure for this particular spec file.

By identifying patterns or trends where these metrics coincide, users can find potential performance bottlenecks that could be causing longer execution times and leading to failures.

A similar analysis can be done on any other metric - the charts provide a visual indication of improvements or regressions in performance and, together with History, allow pinpointing the root cause of change in the performance metrics.

## History

The History shows the recordings matching the selected filters on a timeline - each bar is an execution, its colour is determined by the spec file or test outcome (<mark style="color:red;">**Failed**</mark>, <mark style="color:green;">**Passed**</mark>**,** and <mark style="color:purple;">**Flaky**</mark>), and the height is the relative duration of the recording. Each execution entry provides users with essential information such as the date, time, duration, branch, commit message, and author. Additionally, for failed tests, the feature presents an error preview.

<div data-with-frame="true"><figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2FuHVFS34h0jnprAb0vvcS%2FScreenshot%202026-09-21%20at%2011.23.22.png?alt=media&amp;token=6f605431-6bb1-4883-9605-20caf20681b4" alt=""><figcaption><p>Test History</p></figcaption></figure></div>

Users can use a brush tool to engage with these histograms, enabling them to zoom in and concentrate on executions in a particular period of interest.

### Merge Branches

Users can also arrange executions based on branches using the "Merge branches" flag. This functionality enables a more structured and organized view of the data, grouping the executions according to their respective branches.

{% embed url="<https://player.mux.com/X39d3cnoEQVt47sGl6v1sO7UM01xXHBV37qKSBeeuE74?min-resolution=1080p>" %}
Merge Branches
{% endembed %}


---

# 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/test-suite-performance-explorer/reference.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.