Phase 7: Testing

More rigorous testing, first to check the main functionality of the program, and then to test how the system performs under a heavy usage load. Finally, a test is performed by the client, in the nature of a test drive to compare the finished product to the specification and ensure that he got what he is paying for.

Develop Concurrently! During programming is a very good time to prepare for the testing that will be done when programming is finished. In fact, throughout the development cycle you should look for every opportunity to work concurrently.

Originator: Preferably a third party, but may be either the contractor or the client.

Deliverable: Test plans and scripts annotated with the results of testing. (template)

Components/Steps:

  1. Create Test Plan
    1. Determine Testing Infrastructure (Hardware and OS)
    2. Determine Data Requirements (populate test data)
    3. Create Test Scripts
      1. Business Functional
      2. Load Testing
      3. User Acceptance
  2. Review Test Plan
  3. Implement Test Plan

The House:
The building inspectors have arrived. During this phase they will subject your house to the most rigorous inspection, and will see to it that it not only meets the original specification (Business Functional Testing), but also that it meets the current building codes (Load Testing). When this is done, you as the new owner will give it your own test, independent of any other testing, to see that the work is satisfactory.

Phase 6. Programming Phase 8. Implementation


The informational content of this website is copyright 1997-2002 by David F. Leigh unless otherwise stated. Permission to distribute is granted under the terms of the GNU Free Documentation License.