6.2 Test Plan Checklist

 < Day Day Up > 



Testing Team Considerations

  • Has a Test Lead and/or Team been established?

  • Have vendor responsibilities for testing been established and agreed upon?

Stress Test Plan Considerations

  • Are maximum system stress levels compatible with the user environment?

  • Will existing system stress levels impact performance?

Integration Test Plan Considerations

  • Are all interfaces for the various programs identified and functioning properly?

  • Are manual-to-automated interfaces functioning properly?

  • Are external interfaces with other systems functioning properly?

  • Is data conversion complete and accurate?

  • Is security of the system adequate?

Software Test Plan Considerations (where appropriate):

  • Is internal logic correct and accurate?

  • Do all modules interface correctly in the program?

  • Has internal logic of the program been exercised in the following areas:

    • Statement coverage tests

    • Branch/loop coverage tests

    • Value sampling tests

    • Boundary value coverage tests

    • Program interface tests

    • File-handling tests

    • Error message tests

    • Error-prone tests

User Acceptance Test Plan Considerations

  • Can the user navigate unassisted through the program?

  • Are screen dialogue, volume, and overall usability acceptable to a user?

  • Is all data desired by the user obtainable?

Testing Plan Quality Considerations

  • Have all functions of the product been tested?

  • Have all problem areas been addressed?

  • Have all user problems or complaints been identified and addressed?

  • Have all issues regarding testing been resolved?

The Test Plan Checklist not only requires that the Test Team conduct reviews of the four recommended test plans (i.e., Stress Test Plan, STP, ITP, and UAT) that were created in the previous phase of work, but it also asks for an introspective look at the Test Team and the quality of the test plan. This review helps the team focus on more than just going through the motions of completing a test case; it asks the Test Team members to take responsibility for the validation of the product.

The overall test process should be driven by a quality assurance frame of reference. The Core Team should work carefully with the Test Team to ensure that each test plan designed is properly executed and documented. Ultimately, the SPMO and the Project Manager will have final say on the test execution process because they are accountable to the Project Sponsor for the success of the project.



 < Day Day Up > 



Managing Software Deliverables. A Software Development Management Methodology
Managing Software Deliverables: A Software Development Management Methodology
ISBN: 155558313X
EAN: 2147483647
Year: 2003
Pages: 226

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net