Skip to main content
The analytics dashboard gives you visibility into your testing health across all repositories.

​
Dashboard Stats

The main testing dashboard shows four key metrics:

​
Repository Health

The health visualization shows each repository as a bar:
  • Green = Passing tests
  • Red = Failing tests
  • Gray = Tests not run
Click any repository to drill down into its test details. Track how your pass rate changes over time:
  • Daily pass rate percentage
  • Week-over-week comparison
  • Identify when regressions were introduced

​
Flaky Test Detection

A test is marked flaky when it:
  • Passes on some runs, fails on others
  • Has inconsistent results without code changes

​
Why Flaky Tests Matter

Flaky tests:
  • Waste time investigating false failures
  • Reduce trust in your test suite
  • Slow down development

​
Fixing Flaky Tests

​
Test Duration

See which tests are slow:
  • Average duration per test
  • Duration trends over time
  • Identify tests that have gotten slower
Slow tests increase feedback time and CI costs.

​
Run History

View aggregated statistics:
  • Total runs this week/month
  • Runs by trigger type (Manual, Scheduled, PR, Push)
  • Runs by platform (Chrome, Firefox, Safari)

​
Filtering Analytics

Filter analytics by:
  • Repository - Focus on one repo
  • Time range - Last 7 days, 30 days, 90 days
  • Test type - Unit, Integration, E2E, Performance

​
Exporting Data

Export analytics for reporting:
  1. Go to Testing > Analytics
  2. Set your filters
  3. Click Export
  4. Download as CSV

​
Notifications

Get notified when tests complete.

​
Enable Notifications

Go to Settings > Alerts and configure:

​
Notification Channels

​
Setting Up Integrations

1

Go to Settings > Alerts

Navigate to the alert settings page
2

Click Add Integration

Select your preferred platform
3

Configure Webhook

Paste your webhook URL (or enter email address)
4

Test Connection

Click “Test” to verify it works
You can add multiple integrations. For example, send critical failures to Slack and a summary email to the team lead.

​
Best Practices

Review flaky tests weekly. A few flaky tests can erode trust in your entire suite.
Watch for pass rate drops after deployments—they indicate regressions.
Keep E2E tests under 30 seconds when possible. Long tests are more likely to be flaky.
Schedule tests during off-peak hours to avoid impacting staging environments.
Don’t schedule destructive tests against production if they create test data or modify state.