One of the most common misconceptions about software testing is that QA does not come into play until the development of a module is complete and ready to test.
In actuality, the earlier QA is involved in the Software Development Life Cycle (SDLC) the better. Studies have shown that up to two-thirds of defects can be attributed to requirements and design.
In fact, when you go live, your software shouldn’t be “done.” If it is, you’ve done something wrong.
You see, in the history of software, there’s never been such a thing as a piece of software that launched without bugs. Think of your favorite, most used platforms. Gmail. Facebook. Salesforce. All are brimming with bugs. Every day a user writes into their contact forms about a bug they discovered, and while a lot of them are PEBKAC errors, a lot of them are legitimate bugs. And the ticket tracker logs them, someone triages them, and, eventually, most of them will be corrected.
But before that happens, some new feature will be added, or an existing feature will be modified (‘member when Facebook separated out the messages app from the FB mobile app?), and that will create a whole new series of bugs. (more…)