Latest News from the Thunders Product Team
New feature

Review test changes on a branch before merging them

Ines avatar
Shared by Ines •

Preparing tests for a new feature should not mean changing the version your team relies on today. With branches, you can work on a separate version of your test cases and test sets, run it against the right environment, and bring those changes back to the main branch when you are ready.

The review and merge flow lets you compare the two versions before deciding what to keep. If work on the main branch overlaps with yours, you can resolve the conflicts rather than overwrite the other changes without seeing them.

  • Create a branch from the branch selector and switch straight into it to start editing.
  • Review the differences before merging, including which version comes from the main branch and which comes from your working branch.
  • Resolve conflicts by choosing the version to keep, and bring in changes from the main branch when yours has fallen behind.
  • Keep branch context with your test runs, so you can tell which version of the tests produced a result.
  • Target a branch through the Public API and Thunders MCP as well as in the interface.

#Sprint34