System Test Branch
System test goes on more or less continuously (rather than just at the end of the release cycle). Since system test is all about how the features fit together as whole, we need a stable version of the system to run the tests on. That is, with the exception of bug fixes, we don’t want features being added and updated while system test is going on.
We manage this using system test branches. Whenever we are ready for a new round of system tests, we spawn off a system test branch from the trunk. Since the trunk is always ready for system test (except when we’ve goofed), the test team can do that immediately. The dirty stuff is in the team branches, so there’s no need to wait.
Once we’ve created the system test branch, we deploy ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access