# Test View

For each spec file, the Dashboard displays a list of executed tests **along with insights into their execution**. To analyze a specific test:

**Select the run → Open the “Spec Files” tab → Choose a spec file from the list → Select any test from the test list.**

When you select a test, you can view the[Test Details](/dashboard/tests/run-details.md)and access advanced features such as [#attempts](#attempts "mention")**,** [#console](#console "mention"), [#metrics](#metrics "mention"), [#history](#history "mention"), [#top-errors](#top-errors "mention"), [#annotations](#annotations "mention") **and** [#visual-diff](#visual-diff "mention").

<div data-with-frame="true"><figure><img src="/files/y1yeAgBC8wxiIfH2NFL4" alt=""><figcaption><p>Test View</p></figcaption></figure></div>

## Attempts

For every test attempt, the Dashboard provides the following details:

* **Error Details:** For <mark style="color:red;">**Failed tests**</mark>, the details include the error message and the exact line in the source code (Spec File) where the failure occurs.
* **Screenshots:** Images captured during test execution.
* **Videos:** Full test run recordings.
* **Traces:** Available to open directly in the Playwright Trace Viewer or download.
* **Test Steps:** Detailed test-level analysis . See more at [Step-Level Reporting](/guides/parallelization-guide/step-level-reporting.md).
* **Visual Diff:** Available when enabled the [Playwright Visual Testing](/guides/playwright-visual-testing.md).
* **Attachments:** Any additional files associated with the test.

{% embed url="<https://www.loom.com/share/c1564ee3c4cb497db4b464143ed9bcfe?hideEmbedTopBar=true>" %}
Test View - Attempts
{% endembed %}

For [Flaky Tests](/dashboard/tests/flaky-tests.md), there will be at least one <mark style="color:red;">**Failed**</mark> attempt and one <mark style="color:$success;">**Passed**</mark> attempt. Both show detailed information such as screenshots, videos, traces, test steps, visual diffs, and attachments. **Error details are only shown for failed attempts.** Passed attempts will show the message "**No failures detected**".

{% embed url="<https://www.loom.com/share/eb16e8d9f28e49fd92b2160aa6c28d9e?hideEmbedTopBar=true>" %}
Flaky Tests - Attempts
{% endembed %}

## **Console**

The Playwright console displays each test attempt’s result, including timestamps, expected status, and Currents recording URL, along with any error details. See more details on [Test Status](/dashboard/tests/test-status.md#console-output).

<div data-with-frame="true"><figure><img src="/files/Sz0kKPfUoYI8S6qtMhfn" alt=""><figcaption><p>Console Output - Test View</p></figcaption></figure></div>

## **Metrics**

The Metrics tab provides a summary of the six key metrics available in the Test Explorer:

* **By Flakiness, Status:** Failed Duration vs. Passed Duration and Flaky Duration vs. Non-Flaky Duration.
* **Compared to the Previous Period**: Executions, Avg. Duration, Flakiness Rate and Failure Rate.

For more information on these metrics and how the performance charts work, please check [Test Explorer](/dashboard/test-suite-performance-explorer/tests-explorer.md#test-explorer-metrics) and [Reference](/dashboard/test-suite-performance-explorer/reference.md#performance-charts).

<div data-with-frame="true"><figure><img src="/files/C3CvlwpAuhysnKxq4ZpI" alt=""><figcaption><p>Test View - Metrics</p></figcaption></figure></div>

## **History**

The History tab displays a timeline of test executions, organized chronologically and filterable by branch, history range, and test status. For additional details, refer to [Test History](/dashboard/tests/test-history.md).

<div data-with-frame="true"><figure><img src="/files/uOOmergeiHS9yJO10y0z" alt=""><figcaption><p>Test View - History</p></figcaption></figure></div>

## **Top Errors**

The top errors display the most frequent issues over the past days, with filters for 7, 14, 28, or 45 days. For every error, the Dashboard displays:

* The error message associated with the test failure.
* The number of previous executions where the failure was encountered.
* Chronologically sorted list of the most recent test executions affected by this error. Affected test executions are those that have failed or flaked because of this error.

The Top Errors view also shows some metrics related to each error:

* **Failures**: The number of failed test executions associated with this error. A failed test can have multiple related errors.
* **Failure Ratio**: Proportion of the test failures associated with this error.
* **Flaky**: The number of flaky test executions associated with this error. A flaky test can have multiple related errors.
* **Flakiness Ratio:** Proportion of flaky test executions associated with this error. A flaky test can have multiple related errors.

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

## **Annotations**

Display additional test-related information added through [Playwright Annotations](/guides/playwright-annotations.md), including ownership details, metadata, links to external resources such as Jira tickets or GitHub issues, and any relevant notes.

## **Visual Diff**

Display visual testing outputs generated by Playwright’s native visual comparison features or by third-party tools such as Argos, Applitools, or Percy. See more details at [Playwright Visual Testing](/guides/playwright-visual-testing.md).


---

# Agent Instructions: 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:

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

The question should be specific, self-contained, and written in natural language.
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.