Freeze the Code
Problem: The QA team is having trouble verifying the behavior because the code base keeps changing.
Itʼs much easier to inspect something thatʼs holding still. This is true for code, too. As the release approaches, the testing effort shifts from verifying individual changes to looking at the product as a whole. The QA team needs to have a relatively stable code base to test so they can be sure the release criteria are met. If a test was performed yesterday but the code changes today, how can we be sure it still works without rerunning all of the tests?
A code freeze provides an unmoving code base for testing. Some projects use the term “merge window” instead, which is essentially the time when a freeze isn’t in effect. In either ...
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