Test Runs
Testdino's Test Runs tab is the single source of truth for every Playwright execution in your project. It adds test-aware context on top of CI so you see status, branch, environment, AI labels, and links to evidence in one place. This helps teams answer four key questions quickly: what failed, why it failed, whether it is new or recurring, and where to focus next.
Key Sections in Test Runs
1. Test Run
Shows the Test run ID with the commit message, exact start time, and total duration. The short commit hash and branch name link directly to your Git host so code and tests remain connected.
2. Branch & Environment
Maps each run to the branch and environment where it executed, such as Prod, Stage, or Dev. Results carry real-world meaning because they are tied to where the code ran.
3. Test Results
Aggregates case results for the Test run: Passed, Failed, Flaky, Skipped. This acts as a quick health signal that sets your priority before drilling into details.
These counts come directly from the Playwright report for that run. Testdino reads them as-is.
4. AI Insights
Labels each run with categories like Unstable, Actual Bug, UI Change, or Miscellaneous. This helps reviewers decide if failures are noise or genuine defects.