Test Plan Checklist

Note:  this is a simplified version of a commercially used test plan
  checklist.  Not all of the questions asked are appropriate for all
  testing situations.  So the response to each question can be "yes",
  "no", or "not applicable."

FUNCTIONAL DESCRIPTION
  1.  Is the function being tesed identified.
  2.  Is each requiremnt, which is specified in the appropriate requirements
      document, exercised by the acceptance tests?

TEST PROCEDURE
  1.  Is the testing approach feasible?
  2.  Is there sufficient test coverage to provide confidence that the module
      being tested operates correctly withing its intended environment?
  3.  Is the Test Plan complete and does it have provisions for testing all
      applicable software requirements?
  4.  Does the Test Plan contain the test requirements for each specific
      test case and specify the exact functions to be tested, such as
      input, output, operator actions, display and other requirements that
      are deemed necessary for evaluation?
  5.  Is the evaluation criteria determining success or failure of the test
      defined?
  6.  Are messages verified?
  7.  Are error paths exercised?
  8.  Are return codes tested?
  9.  Have all nominal and extreme test procedures been identified?
  10.  Have illegal and conflicting combinations of inputs been identified?

TEST STRATEGY
  1.  Do the integration test procedures exercise control and data interfaces
      in the corresponding design documents?
  2.  Have integration test procedures been defined to match the order of
      integration?
  3.  For phased delivery, have test baselines been established in each phase
      for use in the next?
  4.  Do any areas require testing which are not addressed by the Test Plan?
      If so, record the problem, continue with the inspection, and then
      resolve offline what error detection operation should include such
      tesing.

TRACEABILITY
  1.  Are the test requirements and criteria traceable to higher level
      requirements documents?
  2.  Does the Test Plan list all the specifications, standards, and
      documents necessary for its development?

REGRESSION TEST
   ... (omitted due to laziness)

BUILD REQUIREMENTS
   ... (omitted due to laziness)

SIMULATION/HARDWARE
   ... (omitted due to laziness)

RESOURCES/SCHEDULES
   ... (omitted due to laziness)

Date Completed:

Participants: