# Using the TestOwl Project Dashboard

:::lead
The Dashboard gives you a high-level view of your project's testing health. It brings together the size of your test library, how your runs are performing, and which tests deserve attention — all in one page.
:::

Open **Dashboard** from the top of the sidebar. The page is titled with your project's name, for example **My Project Summary**. Click **Help** at the top right — it opens **How this dashboard works**, a short in-app guide to every widget.

![Dashboard Overview](/images/getting-started/dashboard/dashboard-overview.png)

## Choosing a time range

Most widgets can be switched between:

- **All** — all time (trend charts show up to the last 90 days).
- **Week** — the last 7 days.
- **Month** — the last 30 days.

Changing the range updates the metrics, trend charts, coverage, and failure list to match.

## Summary cards

The top row shows the size of your library and the value it delivers:

| Card | What it tells you |
| --- | --- |
| **Total Suites** | The number of Test Suites in the project, split into **active** and **draft**. |
| **Total Test Cases** | The number of Test Cases across all suites, split into **active** and **draft**. |
| **Efficiency Gain** | The total time your automated runs have executed. Every hour here is manual testing effort replaced by automation. |

## Metric Summaries

**Metric Summaries** shows key numbers for the selected range:

| Metric | Meaning |
| --- | --- |
| **Total Runtime** | The combined execution time of all runs started in the range. |
| **Total Runs** | How many runs were started in the range. |
| **Pass Rate** | Test-case attempts that completed successfully, divided by every attempt that reached a verdict (passed or failed). Attempts still queued or running are left out until they finish. |

## Pass Rate Trend

The **Pass Rate Trend (%)** chart plots your daily pass rate — based on the test-case attempts from each day's runs — so you can see stability at a glance. A dip means fewer test cases passed that day. Days with no finished attempts appear as gaps in the line.

Use it to spot improvements in stability, recent regressions, or a sudden increase in failures.

## Run Duration Trend

The **Run Duration Trend** chart shows the **average execution time per day**. It catches tests getting slower even while they keep passing, and shows the effect of optimisations. Days without a recorded duration appear as gaps.

## Coverage Overview

**Coverage Overview** lists each [Environment](/docs/environments/overview) with:

- **Coverage** — how many of your **active** Test Cases have been executed at least once in that environment, as a share of all active Test Cases. It turns green at **90% or more**.
- **Pass rate** — how well those tests pass in that environment.

Low coverage means untested environments — for example a mobile or Safari environment that few tests have run against.

If you haven't run anything yet, it shows **No coverage data**.

## Critical Failures

**Critical Failures** ranks your most unstable Test Cases by failure rate across all their attempts, showing "X of Y attempts failed" for each. The list shows the top ten. A **red** bar means more than **20%** of attempts failed; amber is lower.

This is the best place to start debugging: fix the tests at the top first. If everything is healthy it shows **No failing tests**.

## Understanding the numbers

Dashboard statistics are calculated from your project's [Run History](/docs/running-and-results/run-history). Pass rate and failure rate are measured on test-case **attempts** rather than whole runs.

## When to use the Dashboard

- Check the health of your project at the start of the day or before a release.
- Track pass rate and duration over time.
- Find flaky or failing tests quickly.
- See which environments are under-tested.

## Next steps

::::cardgrid
:::card{title="Run History" href="/docs/running-and-results/run-history"}
Browse every test run and open detailed execution reports.
:::

:::card{title="Reports" href="/docs/running-and-results/reports"}
Investigate individual test executions step by step.
:::

:::card{title="Environments" href="/docs/environments/overview"}
Improve coverage by running tests against more environments.
:::
::::