If ever some pious programmer comes up with statements such as, "My code doesn't have any bugs in it," or "I've given it a quick test and it seems to be OK," consider this nothing more than a ruse to get you off their backs. Such statements are unrealistic and unprofessional. Ultimately, this is a sackable offense. Removal of bugs is key to you being able to release working, saleable programs.
Bugs don't unilaterally surrender themselves; you have to go in and route them out. Exhaustive testing of software is impossible, but the following sections present some practical ways to go about it, starting with internal testing both formally and informally, and then going on to public beta test scenarios and how to manage them.
Was this article helpful?