Testing is believed to result in a higher quality end-product, but how much of the software development lifecycle do you think should be spent on it?
In reality, the word testing should change to quality. The key point is: how do you drive quality into software delivery?
You cannot keep testing in hopes that the product will suddenly become something of high quality. That is the fundamental misconception about testing.
A product is only of high quality if it's designed and engineered to be of high quality.
The new world order is doing everything in parallel. So while one designs it, the other creates test cases, and another focuses on virtualisation, release automation asset, performance test, security tests etc. Everything happens at the same time.
In terms of the development effort, the percentage is actually zero because one thinks, designs, codes it and tests it in parallel. It's just changing the way one develops software.
Sign up for Computerworld eNewsletters.