Step 8 -- Generate Test Cases


  • Examine system documentation

  • Examine developer test case inputs and outputs, repeat or extend as needed

  • As a result of interviewing users and developers

  • Examine code

  • Simple (run a case to see how it works)

  • Typical (most actual cases fall into this level of difficulty)

  • Stressful

  • Test vs. requirements, not just as-built

  • Verification tests vs. validation tests (requirements vs. user needs)

  • Includes creating test harnesses (cheaper if done in parallel with development)

  • May need to create pre- or post-processors (cheaper if done in parallel with development)

  • Include inputs, expected outputs, acceptability criteria

  • Acceptability criteria may include run time, disk, or CPU usage

    • The Eleven Steps In VV&A:

    1.     Examine Process Documentation
    2. Examine System Documentation
    3. Interview Developers
    4. Interview Users

    5. Examine Code 1 (Look For Problems)
    6. Examine Code 2 (Break It)
    7. Determine Truth

    8. Generate Test Cases
    9. Run Test Cases
    10. Review Test Case Output
    11. Assessment


    Software Development Plan (SDP) Template
    Software Configuration Management Plan (SCMP) Template
    Software Quality Program Plan (SQPP) Template
    Work Breakdown Structure (WBS) Template

    Introduction
    What And Why Of VV&A