Branch Review
What you'll learn​
- How to compare test results between branches in Cypress Cloud
- How Branch Review surfaces the impact of Pull Requests on your test suite
- How to compare any two runs, if not using a Pull Request workflow
- Best practices for grouping test runs
Cypress Branch Review allows you to quickly identify the different impacts a Pull Request might have on your test suite in a single view. Compare which tests are failing, flaky, pending, added, or modified between the source and base branches. If enabled on your account, UI Coverage or Cypress Accessibility changes between runs will also appear here.
Branch Review is useful even if you do not have a Pull Request workflow, because it allows you to compare any two runs of your choice. These might might represent different builds of the application, changes in test code, or results from nightly runs. This page will use the example of a Pull Request made using the GitHub integration, but this integration is not required in order to use Branch Review.
A common scenario throughout the software development lifecycle (SDLC) is an engineer's feature branch that will be merged into the repo's develop or main branch. Here's how this scenario appears in Branch Review:

Without Branch Review, pinpointing changes in your test suite's results requires a manual side-by-side comparison between your newly-introduced branch's test runs and your base branch's test runs. This sub-optimal workflow often fails to answer the fundamental questions, what changed and why? You might be left wondering if the same tests are flaky between branches, when new failures were introduced, or if you added sufficient test coverage to your new branch.
Getting Started​
The key to the Branch Review area is a comparison between a Base run and a Changed run. The Changed run is the main subject of the comparison, often associated with an incoming Pull Request. The Base run is the starting point for comparison.
Accessing Branch Review​
There are a number of ways to get to Branch Review depending on where you are looking at your Cypress results. In all cases, once you've picked Changed run, you can adjust the automatically-selected Base run to any branch or run in the project to dial in the comparison you are most interested in.
From the project list​
The project card shows three active branches for the project. You can click through to any of these to enter Branch Review focused on that branch.

From the main navigation​
When a project is open, select "Branches" in the main navigation to see a full, filterable list of available branches and choose one to set as the source of the Changed run.

From the run overview page​
Click the branch name associated with the run. This will take you to Branch Review with that run pre-selected as the Changed run. This is a great way to investigate a specific run with an unexpected outcome in the tests.

From a Pull Request​
Click the "View all changes introduced in this branch" link at the bottom of the Test Results table. You will enter branch review with the current PR's branch and latest run pre-selected as the Changed run.
