ABSTRACT
We need a test process that is closely integrated with whatever software life-cycle the project believes it is using and that brings discipline to the manner in which the what-to-test, when-to-stop, and whodoes-what questions are answered. Testing requirements at each phase of the project have to be defined. The cycle shown in Figure 6.1 is very simple, obvious, and true for (almost) any kind of test.
