1. Test Plan 1209

2. Objectives of Test Plan Product –May need to sell test plan Military mil spec FDA specs Phone company (need to support after your company has disappeared) Tool –Helps manage testing project and discover and fix bugs

3. Testing Documentation Facilitates task of testing Improves communication about testing Provides structure for –Organizing –Scheduling –Managing

4. Technical Task Improve test coverage Avoid repetition Improve test efficiency Provide structure for final tests

5. Initial Test Materials Test against documentation Create test documentation that is organized for efficient testing: start a function list Do simple analysis of limits Identify most likely errors Identify most visible errors Identify the most often used areas

6. Things to put in test plan Lists/Tables Outlines Matrices

7. Things to put in test plan Lists/Tables –Files –Features and Functions –Inputs and Outputs –Error messages Outlines Matrices

8. Things to put in test plan Lists/Tables Outlines –E.G. Function list –List top-level, user-visible functions –List subfunctions (options or submenus) –Entry and exit conditions on fully parameterized methods Matrices

9. Things to put in test plan Lists/Tables Outlines Matrices –List function/operation vs test conditions –E.G. the save operation with the following conditions: disk full, almost full, write- protected, …

10. Notes for the test plan How to run test Expected results Special instructions One-shot or regression test What test is looking for Assumptions in the test

11. 3. Testing Approach Specify types of tests to be performed List specific tests Test descriptions are in section 5 May include –Test Management Requirements: how testing is to be managed –Personnel Requirements –Hardware Requirements –Software Requirements –Cost

12. Approach Who does it Techniques and activities When is a group of features adequately tested Constraints: deadlines, availability of people

13. Section 5 and later Test No. Current Status (Passed / Failed / Pending) Test title Testing approach STEP, OPERATOR ACTION, PURPOSE, EXPECTED RESULTS Concluding Remarks Testing Team Date Completed:

14. Post-Installation Test Plan Collect whatever tests pass at installation time Document these as the “test plan” From Lee Copeland, A Practitioner’s Guide to Software Test Design, Artech House Publishers, 2004.

15. Test Template Test No.: > Current Status: > Test title: > Testing approach: > STEP OPERATOR PURPOSE EXPECTED COMMENT ACTION RESULT Concluding Remarks:Testing Team: > Date Completed: