> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testdino.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Playwright Test Analytics in TestDino

> Build a custom analytics dashboard for a Playwright project with saved views, drag-and-drop widgets, and shared layouts.

Analytics is a customizable dashboard for a project. Add widgets to a grid, arrange them, and save the layout as a view. Each view holds its own set of widgets, so different people can track different things in the same project.

## Quick Reference

| Topic                           | Section                                 |
| :------------------------------ | :-------------------------------------- |
| Views (saved dashboards)        | [Views](#views)                         |
| Add and arrange widgets         | [Build a dashboard](#build-a-dashboard) |
| Global time window and platform | [Filters](#filters)                     |
| Share a view with the project   | [Share a view](#share-a-view)           |
| Every widget you can add        | [Widget reference](#widget-reference)   |

## Views

A view is a saved dashboard: a named layout of widgets. A project can hold several views, and you switch between them from the **View** menu in the toolbar.

| View type   | Who sees it             | Badge   |
| :---------- | :---------------------- | :------ |
| **Default** | Everyone in the project | Default |
| **Shared**  | Everyone in the project | Shared  |
| **Private** | Only you                | Private |

Every project starts with 1 **default** view, created automatically. The default is shared with all project members. You can create your own views, keep them private, or share them.

**Create a view:**

* **Create new view** starts a blank canvas.
* **Save as my view** copies the current board into a new private view.

Name the view in the dialog, then add widgets.

<Note>
  Which view you have open is remembered per browser. Switching views does not change what your teammates see.
</Note>

## Build a dashboard

Click **Edit layout** to enter edit mode, then arrange the board:

* **Add** a widget with **Add widget**, which opens a drawer of every available widget grouped by category.
* **Move** a widget by dragging its handle.
* **Resize** a widget from any corner.
* **Remove** a widget with the X in its top-right corner.

Click **Save changes** to persist the layout, or **Cancel** to discard your edits. A new widget drops into the first free space on the grid.

## Filters

2 filters apply to every widget on the dashboard. Both persist as you switch views.

| Filter      | Options                                        | Default       |
| :---------- | :--------------------------------------------- | :------------ |
| Time window | Last 7, 30, or 90 days                         | Last 30 days  |
| Platform    | All platforms, or a single browser or platform | All platforms |

Trend widgets also take an optional per-widget branch or environment filter, set on the widget itself. A few widgets, such as tag and error breakdowns, use their own scope and ignore the platform filter.

**Refresh** reloads the data for every widget. The toolbar shows how long ago the dashboard was last refreshed.

## Share a view

Sharing controls whether other project members can open a view.

| Action                    | Who can do it                |
| :------------------------ | :--------------------------- |
| Share or unshare a view   | The view's creator           |
| Rename or delete a view   | The creator, or an org admin |
| Set a view as the default | An org owner or admin        |

A private view must be shared before it can become the default. The default view cannot be deleted.

## Widget reference

Add widgets from the **Add widget** drawer. They are grouped into 4 categories.

### Reliability

| Widget                 | What it shows                                                          |
| :--------------------- | :--------------------------------------------------------------------- |
| **Health at a glance** | Pass rate, flakiness, p95 duration, and reliability, each with a trend |
| **Pass rate trend**    | Run pass rate over time                                                |
| **Flakiness trend**    | Flaky-run rate over time                                               |
| **Flakiest tests**     | Tests with the most unstable, inconsistent results                     |
| **Most-failing tests** | Tests that fail most often, with their top error                       |
| **Chronic failures**   | Tests that stay broken over time, with a reason                        |

### Performance

| Widget              | What it shows                                  |
| :------------------ | :--------------------------------------------- |
| **Slowest tests**   | Tests ranked by p95, p99, and average duration |
| **Degrading tests** | Tests getting slower over time                 |
| **Duration trend**  | p50 and p95 run duration over time             |
| **Coverage trend**  | Code coverage over time across runs            |

### Errors

| Widget             | What it shows                                |
| :----------------- | :------------------------------------------- |
| **Error clusters** | Repeated failures grouped by error signature |

### Tags

| Widget            | What it shows                       |
| :---------------- | :---------------------------------- |
| **Tag breakdown** | Test distribution and health by tag |

## Related

<CardGroup cols={2}>
  <Card title="Test Explorer" icon="magnifying-glass-chart" href="/platform/playwright-test-explorer">
    Find failing, flaky, or slow tests across the project
  </Card>

  <Card title="Test Runs" icon="play" href="/platform/playwright-test-runs">
    View and debug individual test runs
  </Card>

  <Card title="Code Coverage" icon="chart-bar" href="/guides/playwright-code-coverage">
    Set up Istanbul coverage collection
  </Card>

  <Card title="Organization Analytics" icon="chart-line" href="/platform/organizations/analytics">
    Compare health across every project in your org
  </Card>
</CardGroup>
