Pull Requests
Overview

Pull Requests

TestDino’s Pull Requests view lists each PR with its latest test run and a compact result summary. It adds test context (run, commit, branch, environment) so reviewers see risk before opening code.

Use it to spot blockers, open the run for evidence, and track stability over the life of the PR.



Why This View Matters

  1. Run context at a glance - See the latest Test run ID, start time, duration, and pass/fail/flaky/skipped counts per PR.

  2. Open for proof - Click a row to open the run with failure clusters, specs, logs, screenshots, and console output.

  3. Separate noise from risk - Flaky labels distinguish instability from real failures, so reviews focus on true blockers.

  4. History you can verify - Expand a PR to view all test runs and confirm whether retries or fixes stabilized the tests.

  5. Fast handoff - Jump from a PR to the failing run or test case to file an issue or continue triage.

Layout

PR layout

1. Pull Request

Shows the PR title, number, author, and a state badge (Open, Closed, Merged, Draft). You can click the title to open the PR in your Git host. The badge tells you if the PR still needs review (Open/Draft) or is finished (Merged/Closed).

  • Open - Active PR under review. New commits trigger runs; results update here.

  • Draft - Work in progress. Checks may run, but the PR is not ready to merge.

  • Merged - Changes have been integrated into the base branch. The page retains the history for reference.

  • Closed - PR closed without merging (or after a revert). History remains; no new runs are triggered.

2. Latest Test Run

Displays the most recent run tied to the PR, with run ID, start time, and duration. Click a Test Run to see its detailed view.

3. Test Results

Compact counts for Passed, Failed, Flaky, and Skipped. Use these numbers to spot risky PRs in seconds and decide whether to review, fix, or rerun.

4. Row Expander

Expand a PR to see the full run history. Each entry lists the run ID, timestamp, duration, and result badges so you can confirm if a fix reduced failures or if flakiness persists.

5. Filters and Controls

Search by PR title or number. Filter by Status and Author to focus the list. Sort by Newest (or other order) and use Sync to refresh with the latest runs.

Quick Start Steps

  1. Set scope - Filter by Status and Author, then sort by Newest.

  2. Scan rows - Check the Latest Test Run and Test Results to judge risk.

  3. Open or expand - Expand a PR to review run history; open a test run to inspect evidence (Summary, Specs, History, Configuration, AI Insights).

What You Get Beyond GitHub Checks

  • Test-aware list, not just checks. See the latest test run per PR with pass/fail/flaky counts in the table, without opening CI pages.

  • Actionable triage in one place. Jump from a PR row straight to full run evidence and create Jira/Linear issues from there (See Integrations).

  • Flake and regression detection. View run-to-run patterns for the same PR to confirm fixes or spot recurring instability.

  • Environment and branch context. Results are mapped to environments (dev, stage, prod) so you can judge production impact quickly (See Branch Mapping).

Test CasesOverview