Quality Assurance Testing Phase

In this phase, the system and its user documentation are tested following the test scripts created and finalized in the Construction phase. Problems are reported to the developers, and corrections are made as required, and the User Acceptance Test system is built.

The team may be changed for this phase to add specific testing skills, and must include at least one client from an earlier phase. The QA tester(s) should be from DMS, but not from the project team. If this is not possible, the tester at least should not have worked on the unit(s) being tested.

Deliverables

QA Test Results and Error Reports
These are the documented results of each test, and the reports returned to the developers describing the problems discovered during testing. For a large development effort, a formalized procedure should be followed for communicating results of tests and corrections of known problems back and forth between testers and developers. These reports are part of that formal procedure.
QA Evaluation Sign-off
This is a form, signed by the QA representative, that indicates that the system, documentation, and training materials have passed all tests within acceptable margins. There is no sample available for this form at this time.
User Acceptance Test System
This is the system that will be used for User Acceptance testing, and is created from a frozen development system. Any problems identified during User Acceptance testing will be corrected and unit tested in the development system, which will then be used to recreate the User Acceptance test system.
User Acceptance Test Installation Procedures
These are the procedures that will be used to install the system in the User Acceptance test environment (including client workstations, as needed). As much as possible, this procedure should be the same as the procedure that will be used for production installation, so that the procedure can be adequately tested.
Updated Project Plan
The project plan is updated as needed, and a phase section containing the work breakdown structure and schedule for the next phase is added. At this time, no sample is available.
Methodology Compliance Form
This form is initialized by the project team, and completed by a methodology representative who has reviewed the project documentation and found it acceptable. It is completed in Word.

At this time, no sample is available.

Steps

  1. The QA representative receives the complete system, with documentation and test plan, from the developers.
  2. The QA testers run all tests detailed in the test plans, including tests of the installation and the online help, according to the scripts developed during the design and construction phases. The QA testers should also review any hardcopy user documentation for accuracy and usability.
  3. The testers document the results of each test, and provide error reports and correction requests to the appropriate developers (or writers).
  4. The developer(s) and writer(s) correct the system, installation procedures, and online help, as required.
  5. Repeat steps 2-4 as often as needed, until the system and documentation pass all the tests within acceptable margins.
  6. The QA test team or the project team completes the Testing Checklist for application transition deliverables.
  7. The QA representative signs-off using the QA Evaluation Sign-Off template.
  8. The developer(s) and writer(s) create the User Acceptance Test system and installation procedures, using the frozen development system containing all the corrections discovered during QA testing.
  9. The team gathers all the testing documentation together, and forwards it to the methodology representative for review.
  10. The methodology representative reviews the testing documentation and completes the compliance form before returning the materials to the project team.
  11. The core team reviews the project plan, and updates the schedules and resources, if necessary.