There are two ways to test software. One is to set your sights on the target and attack. Another is to move along and attack bugs as you come across them.
- Before testing begins, the testing person should understand what is to be tested (might be the functional flow), how it should be tested (the way of inputs), and where it could be completed (result). To fix the target, you write test cases, applicable validation and the expected results, and then you start testing.
- However the test cases have been made, you cannot move along the way at all. Some bugs might stand outside your direct path that can create issues later. Although the target is fixed, testing personal should take care of the other bugs that they find during testing, such as software standardization, logical mistakes, validation failure and runtime errors. They should take notes about the test cases that say where and how they identified the bugs.
Testing is like a battlefield. Although the target is fixed, the soldiers should always be alert about their intermediate attacks.
This was first published in November 2007