Managing the Testing Process: Practical Tools and Techniques for Managing Hardware and Software Testing

2.10. Entry Criteria

Entry criteria spell out what must happen to allow a system to move into a particular test phase. These criteria should address questions such as:

• Are the necessary documentation, design, and requirements information available that will allow testers to operate the system and judge correct behavior?

• Is the system read y for delivery, in whatever form is appropriate for the test phase in question?^[]

  ^[] In the component test phase (assuming that the test organization is involved at that point). I usually accept whatever development is read y to provide as long as it includes sufficient scaffolding, or harnesses to run my tests. Once I reach the system test phase, however, I ask for customer packaging, especially in the case of software, whose installation process has a significant impact on whether the system works at all.

• Are the supporting utilities, accessories, and prerequisites available in forms that testers can use?

• Is the system at the appropriate level of quality? Such a question usually implies that some or all of a previous test phase has been successfully completed, although it could refer to the extent to which code review issues have been handled. Passing a smoke test is another frequent measure of sufficient quality to enter a test phase.

• Is the test environment—lab, hardware, software, and system administration support—ready?

Figure 2.3 shows an example of entry criteria that might apply for SpeedyWriter.

2.10.1. Continuation Criteria

Continuation ...