Never time to do it right, always time to do it over
Venting ...
Every time we're testing a build with major new functionality, someone comes up with "critical" issues that need to be addressed first. We put the new build on the shelf and start a new release branch. Then hey, while we're testing this new thing, let's stuff in these other issues, because they can't wait for the shelved release to be brought back out of mothballs.
Eventually we get back to the shelved thing, and shortchange testing on it because now it has become critical - what, you thought we'd get back to it otherwise?
If regression testing finds previously unknown production issues, how did the previous regression testing not find them?
[sigh]
Every time we're testing a build with major new functionality, someone comes up with "critical" issues that need to be addressed first. We put the new build on the shelf and start a new release branch. Then hey, while we're testing this new thing, let's stuff in these other issues, because they can't wait for the shelved release to be brought back out of mothballs.
Eventually we get back to the shelved thing, and shortchange testing on it because now it has become critical - what, you thought we'd get back to it otherwise?
If regression testing finds previously unknown production issues, how did the previous regression testing not find them?
[sigh]
