By default, all newly created tests are saved to a master branch, unless specified otherwise. If you want to make isolated changes to your tests and flows without affecting the version on the master branch, you can save your changes to a branch. This article explains how to add tests and flows to a branch.
When to create branches
Branching in mabl is best-suited for working on development of new features or experimental changes without disrupting the master branch.
When you save tests and flows to a test branch in mabl, you cannot pull subsequent updates from master to the test branch. For this reason, we recommend against using branches for changes that require staying in sync with the latest master version.
Add tests and flows to a branch
To add a test or flow to a branch, take the following steps:
- Launch the test or flow in the mabl Trainer or API Test Editor
- From the branch dropdown, select the branch you’d like to save the test in. Alternatively, create a new branch. Once you create a branch, you cannot rename it.
- Edit the test or flow as needed.
- Click Save. All changes to the test or flow steps are saved to a branch.
Only changes to the test or flow steps are saved to a branch. Metadata, including names, descriptions, and labels, are not version controlled.
When you’re ready to merge your branched tests and flows back into master, follow these steps to safely resolve conflicts and merge.