Skip to main content
The Pull Requests view lists all PRs with their latest test runs. Click any PR to open a detailed view with three tabs: Overview, Timeline, and Files Changed.

Why Use This View

BenefitDescription
Run context at a glanceSee run ID, duration, and pass/fail/flaky/skipped counts per PR
Open for proofClick a row to view failure clusters, specs, logs, screenshots, and traces
Verifiable historyExpand a PR to see all runs and confirm if the retries stabilized tests
Fast handoffJump from PR to a failing run or test case to file an issue
Integrated code reviewReview diffs in Files Changed alongside test results
Filterable timelineTrace which commits led to specific failures or fixes

Layout

Pull Requests list view showing PR metadata, test run results, and status columns Each row represents a PR and includes:
  • Pull request metadata: title, number, author, and state
  • Latest test run: test run ID, start time, and duration
  • Test results summary: counts for passed, failed, flaky, and skipped
  • Row expander: full run history for that pull request

Pull Request State

Shows PR title, number, author, and state badge.
  • Open: Active PR under review. New commits trigger runs.
  • Merged: Changes integrated into the base branch. History retained.
  • Closed: PR closed without merging. History remains, but no new runs trigger.
Click the PR number to open the PR in GitHub or your CI provider.

Filters and Controls

Use the controls to narrow the list and refresh data:
  • Search by pull request title or number
  • Filter by status and author
  • Sort by newest (or other available sort order)
  • Sync to refresh the list

Pull Request Detail View

Select a pull request to open its detail view.

Overview

Use this tab to review the current test health for the pull request and open the latest run for deeper debugging.

Timeline

Use this tab to correlate activity over time. It can include:
  • Commits
  • Test runs
  • Pull request and code comments
Use the timeline to identify when failures began and whether subsequent runs improved.

Files Changed

Use this tab to review code diffs associated with the pull request while keeping test results in context.

Quick Start Steps

1

Set Scope

Filter the PR list by Status and Author.
2

Scan Rows

Scan the Latest Test Run and Test Results columns to identify risky pull requests.
3

Open Detail View

Click any PR row, and open the pull request detail view.
4

Analyze Context

Use Overview for current status, Timeline for cause and sequence, and Files Changed for the related code diff.
If needed, open a failing run to inspect logs, screenshots, traces, and console output.

What You Get Beyond GitHub

FeatureDescription
Test run summary per PRView all test runs per PR with pass/fail/flaky counts without opening CI pages
One click triageJump from PR to full test run and create Jira, Linear, Asana, or Monday issues
Flakiness visibilityView run-to-run patterns to confirm fixes or spot recurring instability
Environment contextResults mapped to environments (dev, stage, prod) for quick impact assessment
Code diffs in contextFiles Changed shows additions and deletions alongside test results
Timeline filteringFilter by event type to show only test runs, commits, or comments