> 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/insights-and-analytics.md).

# Insights and Analytics

Currents Dashboard Insights allows you to analyze the behaviour and dynamics of your Playwright or Cypress test suite over time. You can use the insights to track the performance of your runs/build and tests over time and to identify the most problematic tests - most flaky and most failing - that are worth fixing.

{% embed url="<https://www.loom.com/share/5e9729f553674032a5a7ce96c5786010?hideEmbedTopBar=true.&hide_owner=true&hide_share=true&hide_title=true>" %}
Currents Analytics&#x20;
{% endembed %}

See the notes below to discover how specific metrics are getting calculated.

### Runs Status

Represents distribution of the outcomes of your builds/runs over time.&#x20;

![Example chart - Runs Status Insights](/files/YGfGhHhKOhatE3zMaWWg)

* Overall runs - overall runs created during the selected period, regardless of their completion or the end state
* Failed runs - runs that have 1 or more failed tests. Failed runs count includes cancelled and timed-out tests.
* Passed runs - runs that have 0 failed tests. Passed runs count includes cancelled and timed-out tests.
* Pass Rate - passed runs / overall runs

### Runs Duration

Runs Duration chart represents the daily/weekly average duration of **fully reported** runs. A fully reported run is a run that wasn't cancelled and didn't time out.

**Please note** that cancelled or timed-out runs are excluded from the report.

![Example chart - Runs Duration Insights](/files/DhbzouNWgLEojaeCQhFh)

### Runs Completion

Runs Completion chart represents the distribution of runs by their completion over time.

![Example chart - Runs Completion](/files/GDd2ShKLUuoULRKWkaKk)

* Overall runs - overall runs created during the selected period, regardless of their completion or the end state
* Fully reported runs -  runs that weren't cancelled and didn't time out
* Cancelled runs - see [Canceling Runs](/~/changes/TYKBeqcc7WyqjmgOzWzB/dashboard/runs/cancel-run.md)
* Timed out runs - see [Run Timeouts](/~/changes/TYKBeqcc7WyqjmgOzWzB/dashboard/runs/run-timeouts.md)

### Spec / Tests Size Chart

Specs / Tests size chart represents the **maximum** daily/weekly amount of specs/tests for fully completed runs. A fully reported run is a run that wasn't cancelled and didn't time out.

**Please note** that cancelled or timed-out runs are excluded from the report.

![Example chart - Run Specs / Tests Size](/files/wByz7mhuVSsb063itsgP)

* Spec files - the **maximum** number of spec files detected in a run for the selected period
* Tests - the **maximum** number of tests detected in a run for the selected period

### Test Results Chart

Test Results Chart shows the distribution of tests outcome over time.

![Example chart - Test Results](/files/P4JoSII6m35HJpjmlbbA)

* Total tests - overall tests recorded for the selected period, regardless of their outcome
* Passed tests - tests that successfully completed all attempts without any exceptions or errors during its execution
* Failed tests - tests that either failed or were skipped because of an error in `beforeEach/beforeAll`
* Ignored test - tests that weren't run e.g. `it.skip()`
* Success Rate - `passed  / (total - pending)`

### Tests Flakiness Chart

Test Results Chart shows the distribution of flaky tests over time.

<figure><img src="/files/V8XzL0RIW9TQf9dqB1sT" alt=""><figcaption><p>Example chart - Tests Flakiness</p></figcaption></figure>

* Flaky tests - overall flaky tests detected for the period. See [Flaky Tests](/~/changes/TYKBeqcc7WyqjmgOzWzB/dashboard/tests/flaky-tests.md)
* Flakiness rate - `flaky tests count / passed tests count`


---

# 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/insights-and-analytics.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.