1 Test Planning CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 9, 2007

2 Outline Process for planning Test plan components

3 Test Planning Process 1. Define test strategy 2. Define test system 3. Estimate test effort 4. Prepare and review test plan

4 1. Test Strategy Scope  You cannot test everything.  What are the priorities? most important features new code most difficult areas most often used features int sum(int a, int b){ int r = a; while (b > 0) { r++; b--; } return r; }

5 1. Test Strategy (continued) Approach: When to do different tasks Entry/exit criteria  When can you start?  When can you stop?  When can you restart? Automation  Which tools?  When? (e.g., only regression testing)

6 2. Test Systems Architecture  Test suite: collection of tests for a related group of requirements  Test: one or more test cases for a single function or requirement  Test case: smallest unit Environment: physical facilities Configurations: platforms, combinations

7 3. Estimating Test Effort Tasks: list of things to do Effort estimation: previous experience, expert judgment (Delphi), decomposition Schedule: show relationships between tasks Risks: estimate likelihood and impact

8 Delphi Experiment

9 Cartoon of the Day

10 Components of a Test Plan 1. Test plan identifier 2. Introduction 3. Test items 4. Features to be tested 5. Features not to be tested 6. Approach 7. Item pass/fail criteria 8. Suspension criteria and resumption requirements 9. Test deliverables 10. Testing tasks 11. Environmental needs 12. Responsibilities 13. Staffing and training needs 14. Schedule 15. Risks and contingencies 16. Approvals

11 Test Plan Components (1) 1. Test plan identifier: unique 2. Introduction: objectives of document 3. Test items: high-level description of inputs to testing 4. Features to be tested: list of features or requirements 5. Features not to be tested: features you cannot test yet

12 Test Plan Components (2) 6. Approach how you will test may include: phases of testing (unit, system, acceptance), static vs. dynamic methods, performance testing, regression testing, use of problem tracking system 7. Item pass/fail criteria When does a test pass? When does the product pass?

13 Test Plan Components (2) 8. Suspension criteria and resumption requirements: what to do if bugs prevent progress 9. Test deliverables: all outputs of testing 10. Testing tasks: from your schedule 11. Environmental needs: hardware and software 12. Responsibilities: who does what

14 Test Plan Components (3) 13. Staffing and training needs: list people or types of people 14. Schedule: milestones 15. Risks and contingencies: matrix here 16. Approvals: signatures