Test Runs
Overview

Test Runs

TestDino’s Test Runs tab is the single source of truth for every Playwright execution in your project.

It adds context on top of CI with status, branch, environment, AI labels, and links to evidence, so you can see what failed, why, whether it is new or recurring, and where to focus next.


What You See

Use search and filters to scope runs, then open a row for detailed triage.

Search and Filters

ControlsPurposeOptions
SearchFind runs by text or IDCommit message, run number (for example, #1493)
Time PeriodLimit runs to a date rangeLast 24 hours, 3 days, 7 days, 14 days, 30 days, Custom
Test StatusFilter by outcomePassed, Failed, Skipped, Flaky
DurationSort by runtimeLow to High, High to Low
CommitterShow runs by authorSelect one or more committers
EnvironmentFocus on a mapped environmentproduction, development, hotfix
BranchFocus on branchesSelect one or more branches

Test Run Key Columns

  1. Test Run shows the ID, start time, and CI or Local Executor. Click the CI label (for example, GitHub Actions) to open the CI job.

  2. Commit contains the commit message, short SHA, and author. Links to the commit in your Git host (If it exists in the project).

  3. Branch & Environment tells you the branch and the mapped environment label for that test run. (Mapped in Branch Mapping)

  4. Test Results list the counts for Passed, Failed, Flaky, and Skipped, plus the total.

  5. AI Insights display the category counts for Actual Bug, UI Change, Unstable, and Miscellaneous. Click any row to open run details.

Quick Start Steps

  1. Set scope - Filter by Time Period, Environment, Branch, Committer, Status, and sort by Duration to focus the list.

  2. Scan and open - Review result counts and AI labels, then open a run that needs action.

  3. Review details - The run details page provides five tabs:

    • Summary - Totals for Failed, Flaky, and Skipped with technical sub-causes and derailed analysis of testcases. Use for quick triage.

    • Specs - File-centric view of the run. Sort and filter to find slow or failing specs and tests.

    • History - Outcome and runtime charts across recent runs. Spot spikes and regressions.

    • Configuration - Source, CI, system, and test settings. Confirm environment and detect config drift.

    • AI Insights - Category breakdowns, error variants, and patterns that highlight new, recurring, or high-impact issues.

More on Test Runs