TheAssailant
Well-known member
As someone who works in software testing, I can tell you overlap testing happens all the time...specifically with interim patches. You don't simply halt major testing on a big release when you have to ready a patch that "fixes" one particular area of the software. Nor do you have to re-test the entire application if the interim build only affects a specific portion of the software. That would be unrealistic in terms of time and it would also be an inefficient use of resources.
Once the interim patch has been tested and deployed into production, it's then merged and integrated into the next major release being tested. Re-testing is performed only for the affected area that was patched. Later regression testing will hopefully catch any other anomalies that pop up as an effect of an interim build that was not caught during initial testing (before it was deployed to a production build).
Of course it all depends on how extensive the change is AND not every company's test process is the same as others.
I doubt Verizon would have the foresight to be that efficient. Otherwise IMM76K wouldn't have taken as long as it did.
Sent from my VZW Galaxy Nexus using Android Central Forums