1. Test Planning
And the Test Plan

2. A. Test Planning Approach
Test Plan Guidelines
Goals
Ingredients
Sequence of events
Meet or exceed expectations
Introduce & explain
Prove and document system readiness
Details of QC

3. Test Planning Approach
Is the test plan a tool or product?
Establishing Test Coverage
Linking it to the test requirements
Details of QC

4. Agenda 1. The Hierarchy of a Test Requirement
2. Generating a Test Requirement Hierarchy
3. A quick look at Test Coverage Measures
4. Anatomy of a Test Plan

5. Test Requirements Why identify them?
What exactly is a Test Requirement?
Where does a Test Requirement come from?

6. Drilling down

7. (the infamous) ATM Example
Business Requirements:
- “ATM must do withdrawals”
- “Withdrawals are between $20-$300”
- “Withdrawals are in $20 multiples”
Group Exercise!
1. What tests would you create?
2. What will you validate?
3. Are there any implied requirements that may not be written out?

8. Test Scenarios/Cases for - “Validate that a withdrawal of a multiple of $20, between $20-$300 can be done”

9. Test Procedure & Script for previous example
Script: (in pseudo-code )
Step 1: Insert Card
Step 2: Enter PIN
Step 3: Select Withdraw option
Step 4: Enter dollar amount
Step 5: Validate amount received
Do until EOF ‘until end of data file
Input data record
Senddata CARDINFO to “Cardfield”
Senddata “Enter”
Senddata PIN to “PINFfield”
Senddata “W” to “SelectionField”
Senddata AMOUNT to “DollarField”
If ErrorMsg > 0 then print ErrorMsg
Print “DollarAMTgiven”
Loop

10. 2. Generating a Test Requirement Hierarchy
Remember that different applications organize in different ways
Maintain a level of balance between too much & too little
Generally, organize your testing by Type of Test

11. Test Requirement Decomposition

12. 3. A quick look at Test Coverage Measures
Test Requirements are the “what” of testing
TR’s give us the point of measurement for test coverage
Each TR should be tracked for Verification () and Validation (%)

13. 4. Anatomy of a Test Plan Review the parts of a test plan
Review the process of the test plan creation process
Develop your own template
Who, What, When, Where, Why, & How

14. 3 cardinal rules for test plans
A Test Plan is a contract between the tester and the development team
A Test Plan should always be written for another tester to implement
A Test Plan is a synthesis of the standards & guidelines of your QC process for the particular project

15. Test Plan Scope Disclaimer
The size of a test plan & the effort of creating it, is directly proportionate to the size of the project.
A good test plan, regardless of size, always addresses all the following themes
A successful QC person addresses the entire QC process within the scope of the test plan

16. The Test Plan Process 1. Identify the scope and Test Requirements
2. Identify the Test Priority
3. Develop a testing strategy
4. Identify resources
5. Create the schedule
6. Compile the test plan
7. Test plan is approved and testing is executed
8. Results are documented

17. Some Test Plan Parts 1. Project Definition & Background
2. Target Dates
3. Test Requirements Hierarchy
4. Strategy or Approach for each of the areas of QC
5. Risks & Dependencies
6. Unresolved / Open Issues
7. Resources
8. Document Tracking
9. Results / Summary

18. Review Sample Test Plans
What is Good?
What is Bad?
What is Missing?
General observations?