If we do not regularly review and revise our tests, we'll stop finding defects

Repeatedly running a set of tests will ensure that a system is defect free

Defects are, paradoxically, often contained in a small number of modules

Testing, like spraying pesticide, is an effective bug / defect removal activity

The key to high quality test documentation regimes is strict adherence to this standard

Any deviation from this standard should be approved by management, marketing & development

This test plan outline is relevant for military projects For consumer market projects there is a different specification with fewer items

Most test documentation regimes follow this spec to some degree, with changes done to fit a specific situation or organization

Functional testing to test security at the system level, load testing at the system level to ensure the system availability is acceptable, regression testing at all levels, structure based testing at the component level only

Functional testing to test the use cases at component level, reliability testing to test availability at the integration level, regression testing at the system testing level only, structure based testing at all levels

Functional testing of the use cases at system level, load testing at component level to ensure availability is acceptable, regression testing at the system and acceptance levels only, and structure based testing at the integration level only

Functional testing to test security at the acceptance level, load testing at the acceptance test level to ensure availability is acceptable, regression testing at the acceptance level only to ensure late changes are made correctly, and structure based testing at the component level