Test stabilization with a branch
Preserve approved requirements for testing while development continues with the next generation of features. Use a branch to give a test team a stable, unchanging set of requirements while development continues on the main project.
When to use test stabilization
Use this workflow when the requirements for a release or feature are approved and implemented, but the test team needs time to validate them. The branch preserves the test baseline, so requirements don’t change during the test cycle.
For example, a medical device company can branch the approved requirements for a new insulin pump. The test team validates those requirements while the engineering team continues work on the next generation of features in the main project.
Workflow summary
The test team works from the branch while development continues in the main branch. After testing, the team compares the branches, merges the required and approved changes, and deletes the branch when it is no longer needed.
The workflow includes an approved requirements baseline, a test branch, testing, continued development on the main branch, branch comparison, change merging, and branch deletion.
Branching capabilities
Branch Create
Branch Comparison (Diff View)
Branch Merge
Branch Delete