Lonsdale Systems

Writing Test Plans Course Page

Vehicle Functional System Test Plan
  • 1. Test plan identifier
  • 2. Introduction
  • +- 3. Test items
    • Test artefacts
      • Vehicle
        • Cruise control
          • Board version 1.1
          • Firmware version 2.8
        • Engine management interface version 2.3
    • Test basis
      • Requirements specification
        • Seperate requirements
      • Vehicle operations manual
      • Data logging device manual
      • Safety risk analysis
    • Excluded items
      • Interface between cruise control and EMU
  • +- 4. Features to be tested
    • R1
      • Is a power indicator required?
    • R1, R4, R8 verified indirectly by a single test case
    • R8 Shall maintain stored speed...
  • +- 5. Features not to be tested
    • R2, R3
      • Inspection required
      • Reword "... any driver..."
    • R6, R9
      • R8 but not "... via an interface"
    • All other vehicle systems
  • +- 6. Approach
    • Product risks
      • Death or injury
      • Property damage
    • Strategy
      • Test level
        • System
      • Test objective
        • Verify
        • Failures (secondary)
      • Expected outcome
        • Pass
        • Fail
          • e.g. Set and reset together
          • Set and brake
      • Tester
        • Test driver
      • Test design technique
        • Black box
        • Exploratory (failure)
      • Need to measure enginer power percentage?
    • Test completion criteria
      • 100% of test cases sucessfully executed
  • 7. Item pass/fail criteria
    • All defects with severity greater than 2 repaired
  • +- 8. Suspension criteria and
    resumption requirements
    • Testers safety is threatened
    • Posible damage to vehicle
    • +- Driver unfit
      • Drug and alcohol test?
  • +- 9. Test deliverables
    • Test plan (this document)
    • +- Test specification
      • Design
      • Test case
      • Test procedure
    • Test log
    • Test incident reports
    • Test report
    • Safety approval
  • 10. Testing tasks
  • +- 11. Environmental needs
    • +- Data recording device
      • Record speed only?
    • Test circuit?
    • Rolling road?
    • Device to measure engine power?
  • 12. Responsibilities
  • +- 13. Staffing and training needs
    • Test driver to safety course
    • Training to use data logging device
  • 14. Schedule
  • 15. Risks and contingencies
  • 16. Approvals
Service Report Test Specification
  • 1. Test design identifier
  • +- 2. Features to be tested
    • +- Test items
      • Service report
      • Add new car screen
      • Record car maintenance screen
      • Database
      • Data conversion program
    • +- Test basis
      • Change request
      • Business rules
      • Database design
      • Exisitng user documentation
      • Existing system test plan
    • +- Features
      • +- Add new car screen
        • Exsiting functionality
        • Date of purchase
      • +- Record car maintenance screen
        • Existing functionality
        • Date of last service
        • Mileage at last service
      • +- Service report
        • Car OK
        • Due for service
        • Overdue for service
        • Sell car
      • +- Database
        • Date of purchase
        • Date of last service
        • Mileage at last service
      • Regression test
  • +- 3. Approach refinements
    • +- Test strategy
      • Unit
      • Tester
      • Black-box
      • +- Report, database
        • Verify
        • Test to pass
      • +- Screens
        • Failure (regression related)
        • Test to pass
    • +- Test completion criteria
      • All test cases executed
      • No defects
    • +- Test oracle
      • Spreadsheet
    • +- Common attributes of test cases
      • Input values
      • Environmental needs
      • Procedural requirements
      • Test case dependencies
  • 4. Test identification
  • 5. Feature pass/fail criteria

Tags