> 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/spec-file-status/spec-files-view.md).

# Spec Files View

For every run, the Dashboard displays a list of executed spec files. To analyze a specific run:\
**Select the run** → **Choose the “Spec Files” tab** → **Select any spec file from the list**.

When selecting a Spec File, users can view the [Spec File Details](/dashboard/spec-file-status/run-details.md) and access advanced features such as [Spec Files Explorer](/dashboard/test-suite-performance-explorer/spec-files-explorer.md), the list of [**Tests**](#tests), [**Console**](#console), [**Metrics**](#metrics), and [**History**](#history).

{% embed url="<https://www.loom.com/share/ac07a738cc594d56b24323f059e5d2d7?hideEmbedTopBar=true&sid=40358c18-80a6-4f7b-8a11-ba6c890bc07c>" %}

## Tests

The list of tests in the Spec Files View includes the [Test Status](/dashboard/tests/test-status.md), the number of attempts, start and end timestamps, duration, number of [Playwright Annotations](/guides/playwright-annotations.md), test owners, and direct access to the test artifacts such as screenshots, videos, traces, and visual diffs (if you have enabled the [Playwright Visual Testing](/guides/playwright-visual-testing.md)).

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

#### Filters and Controls

The test list can be sorted by **Status**, **Test Title**, **Duration**, **Start Time**, and **Finish Time**. It can also be filtered by [Playwright Annotations](/guides/playwright-annotations.md) and [Test Status](/dashboard/tests/test-status.md) to help narrow down the results.

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

## **Console**

The Playwright console output displays the result of each test attempt, along with relevant details such as the start and end timestamps, expected status, and the recording URL in Currents.

In case of errors, it provides the error details for each individual attempt. See more details on [Test Status](/dashboard/tests/test-status.md#console-output).

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

## **Metrics**

The Metrics tab provides a summary of the six key metrics available in the Spec File Explorer: Average Duration, Overall Executions, Suite Size, Failure Rate, Flakiness Rate, and Timeout Rate.\
For more information on these metrics and how the performance charts work, please check [Spec Files Explorer](/dashboard/test-suite-performance-explorer/spec-files-explorer.md#spec-files-explorer-metrics) and [Reference](/dashboard/test-suite-performance-explorer/reference.md#performance-charts).

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

## **History**

The History tab presents a timeline of test executions within the Spec File. For additional details, refer to [Reference](/dashboard/test-suite-performance-explorer/reference.md#history).

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


---

# 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/spec-file-status/spec-files-view.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.