Electric Cloud's Juan Jimenez recently blogged:
"Consider this statement of truth – the bane of any Continuous Delivery strategy is testing. You can have wildly fast builds...completely automated Continuous Integration and Delivery... but if your Continuous Testing slows your Agile-ity to a crawl, it’s all for naught, sire.
Consider as well that the number one root cause for software failures is insufficient testing, and the number one reason for that is the time and effort it takes to perform full testing. When there are conflicting priorities, corners are cut and test schedules suffer as a result."
At Parasoft, we couldn't agree more. Unless the process of testing is optimized and streamlined along with the rest of the SDLC, your SDLC acceleration efforts are likely end up releasing bugs to customers at an unprecedented pace. But how can you achieve your quality objectives when you're faced with increasingly rapid and compressed iterations? First off, you obviously want to increase automation, speed up test execution, and reduce the time required to review, prioritize, and respond to test results. But you don't need to stop there. You can also reduce the number of defects that are introduced into the code base in the first place.