Test Plan Checklist-JPL

FUNCTIONAL DESCRIPTION
  1.  Is the description of the function being tesed, as documented in the
      Test Plan, complete and accurate?
  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 function
      being tested operates correctly withing its intended environment?
  3.  Do the integration test procedures exercise each interface described in
      the corresponding design document?
  4.  Are the specific objectives of the test defined and a summary of the
      test methods and the type of system environment to be used included
      in the Test Plan?
  5.  Is the Test Plan complete and does it have provisions for testing all
      applicable software requirements?
  6.  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?
  7.  Are control and incorporation of changes to the specifications, design,
      or coding that may occur during the test contained in the Test Plan?
  8.  Is the evaluation criteria determining success or failure of the test
      defined?
  9.  Are the test plan entrance and exit criteria realistic?
  10.  Are sufficeint numbers of defaults exercised?
  11.  Are messages verified?
  12.  Are error paths exercised?
  13.  Are return codes tested?
  14.  Have all nominal and extreme test procedures been identified?
  15.  Have illegal and conflicting combinations of inputs been identified?
  16.  Are there extraneous or obsolete test procedures which cna be
       eliminated?

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)