> ## 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
> Track test health trends across runs, environments, and time.
export const VideoSchema = ({name, description, thumbnailUrl, uploadDate, duration, contentUrl, embedUrl}) => {
const schema = {
"@context": "https://schema.org",
"@type": "VideoObject",
name,
description,
thumbnailUrl,
uploadDate,
...duration ? {
duration
} : {},
...contentUrl ? {
contentUrl
} : {},
...embedUrl ? {
embedUrl
} : {},
publisher: {
"@type": "Organization",
name: "TestDino",
logo: {
"@type": "ImageObject",
url: "https://docs.testdino.com/logo/light.svg"
}
}
};
return ;
};
**What you'll learn**
* What each analytics view (Summary, Test Run, Test Case, Errors, Coverage, Environment) shows
* How filters work across all views
* How to use analytics to drive stability and speed improvements
Analytics turns test activity into clear trends. Shows what's failing, what's flaky, where time goes, and which environments slow you down.
## Why Analytics Matters
* **Spot real problems fast** - See where failures concentrate and if they're new or repeating
* **Cut noise** - Find and reduce flakiness so reviews aren't blocked by random failures
* **Speed up feedback** - Identify which files, tests, or environments are slow
* **Prove progress** - Trends show when stability or speed improves
## Views
| View | What it shows | Use it to |
| :---------------------------------------------------------------- | :--------------------------------------------------------------------------------------- | :-------------------------------------------------------------------- |
| [**Summary**](/platform/analytics/playwright-test-health-summary) | Total test runs, average runs per day, pass/fail counts, flakiness and failure rates | Assess overall test suite health and spot unstable tests |
| [**Test Run**](/platform/analytics/test-run) | Average and fastest run times, run-level tag health table, performance by branch and day | Compare run times, review tag pass rates, and optimize test execution |
| [**Test Case**](/platform/analytics/test-case) | Average, fastest, and slowest test durations, pass/fail trends | Identify slow tests and track reliability over time |
| [**Errors**](/platform/analytics/errors) | Error messages grouped by type, occurrence frequency, affected tests | Find recurring problems and prioritize fixes by impact |
| [**Coverage**](/platform/analytics/playwright-code-coverage) | Statement, branch, function, and line coverage trends over time | Track coverage changes and detect regressions |
| [**Environment**](/platform/analytics/environment) | Test failures and successes by environment and branch, pass rates over time | Isolate environment-specific issues and focus debugging |
## Filters
All analytics views share a global filter bar at the top. Filters persist as you switch between views.
| Filter | Description | Default |
| :---------- | :------------------------------------------------------- | :--------------- |
| Time Period | Scope data to last 7, 14, 30, 60, or 90 days | 30 days |
| Environment | Filter by mapped environment (staging, production, etc.) | All environments |
| Branches | Select one or more branches to include | All branches |
## Get Started
1. **Set scope** - Select Time range and Environment. Add Branches if needed. Keep these fixed during review.
2. **Review Summary** - Look for spikes in failures, flakiness, or retries. Open the day or metric that stands out.
3. **Select a view** - Use **Test Case** to address slow or flaky tests, **Test Run** to improve run time, stability, and tag health, **Errors** to find recurring problems and prioritize fixes by impact, **Environment** to isolate setup-specific issues.
4. **Apply and confirm** - Implement the fix, then verify the improvement by checking the same charts in the next run or period.
## Explore