Skip to main content
The TestDino Dashboard displays Playwright test data organized by role. QA engineers see failure patterns and flaky tests; developers see branch health and test outcomes.

​
For QA Engineers

  • Pass/fail breakdown of every test run
  • Flaky tests highlighted for quick triage
  • Failure counts and percentages by error type.

​
For Developers

  • Fast feedback on your pull requests and branches
  • Which tests failed after your recent commit
  • Environment consistency (dev vs staging vs prod)
  • Clear signals on which tests are failing or flaky
  • Monitor branch health over time.

​
How the Dashboard Helps Everyone

  • QA gets faster triage.
  • Developers get faster fixes.

​
Quick Start Steps

  1. Open the project - Go to Organization, then select your Project.
  2. Set filters - Choose Period and Environment. An Environment groups one or more Branches.
    • Period sets the time window (7, 14, or 30 days).
    • Environment is where tests run (for example, Development, Staging, Production). An environment can include one or more branches.
    • Branches narrows the view to specific branches inside the chosen environment.
  3. Choose a role view - Select QA or Developer to open the corresponding dashboard.

​
What Each View Offers

Use these cards to know more about each view. Each card opens its own page with screenshots and details.

QA Dashboard

Tiles and panels for failures, flaky tests, and categories.

Developer Dashboard

Active Blockers, Ready to Ship, Flaky Alerts, and branch health.