Phases in a Tester’s Life

Phase 0 : There’s no difference between testing and debugging. Here there is no effective testing, no quality assurance and no quality.\


Phase 1 : The purpose of testing is to show that the software works. Testing increases, software works decreases. There is a difference between testing and debugging. If testing fails the software doesn’t work.


Phase 2 : The purpose of testing is to show that the software doesn’t works. The test reveals a bug, the programmer corrects it, the test designer designs and executes another test intended to demonstrate another bug. It is never ending sequence.


Phase 3 : The purpose of testing is not to prove anything, but to reduce the perceived risk of not working to an acceptable value. Here testing implements the quality control. To the extent that testing catches bugs and to the extent that those bugs are fixed, testing does improve the product. If a test is
passed, then the product’s quality does not change, but our perception of that quality does.


Note : testing pass or fail reduces our perception of risk about a software product.
Phase 4 : Here what testing can do and not to do. The testability is that goal for two reasons :


1.Reduce the labor of testing.
2.Testable code has fewer bugs that code that’s hard to test.