160 likes | 502 Views
Test Planning. CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 9, 2007. Outline. Process for planning Test plan components. Test Planning Process. Define test strategy Define test system Estimate test effort Prepare and review test plan. Scope
E N D
Test Planning CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 9, 2007
Outline • Process for planning • Test plan components
Test Planning Process • Define test strategy • Define test system • Estimate test effort • Prepare and review test plan
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; } 1. Test Strategy
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)
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
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
Test plan identifier Introduction Test items Features to be tested Features not to be tested Approach Item pass/fail criteria Suspension criteria and resumption requirements Test deliverables Testing tasks Environmental needs Responsibilities Staffing and training needs Schedule Risks and contingencies Approvals Components of a Test Plan
Test Plan Components (1) • Test plan identifier: unique • Introduction: objectives of document • Test items: high-level description of inputs to testing • Features to be tested: list of features or requirements • Features not to be tested: features you cannot test yet
Test Plan Components (2) • 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 • Item pass/fail criteria • When does a test pass? • When does the product pass?
Test Plan Components (2) • Suspension criteria and resumption requirements: what to do if bugs prevent progress • Test deliverables: all outputs of testing • Testing tasks: from your schedule • Environmental needs: hardware and software • Responsibilities: who does what
Test Plan Components (3) • Staffing and training needs: list people or types of people • Schedule: milestones • Risks and contingencies: matrix here • Approvals: signatures