Test planing and estimation

Test planing and estimation

Test plan - direction for overall testing activity

Written test plans give us a baseline - Against it we can measure revisions and changes made.
Test Plan Vs. Test Design



Test Plan
Defines overall testing objectives and approach
Provides accurate test estimation

Test Design
Defines what will be tested
Describes expected results



Test Plan Elements:

1. Test Scope - Defines what will be tested
2. Test Objectives - Description of expected (measurable) test result, priority
3. Assumptions - Include skill level of testers, budget, starting state of application, tools & equipment availability, etc.
4. Risk Analysis -Things that could impact testing ability
5. Test Design - Identifies tests to run, stages to test, outlines sequence and timing
6. Roles & Responsibilities
7. Test Schedule & Resources - Major test activities, sequence of tests, estimates, dependence on other activities, people, tools, facilities
8. Test Data Management - Methods for preparing test data, backup/rollback procedures, data requirements/sources, any data conditioning/conversion, data security
9. Test Environment - Version Control, HW/SW configurations, defect tracking tool, Environment for each kind of testing
10. Communication Approach - Meetings, processes, tools, techniques, contact lists
11. Test Tools - Automation, performance, verification, defect tracking, test planning, etc.

Also can be added:
- What metrics should be used
- Entry criteria
- Exit criteria

Test Prioritization

Time and budget are never enough
Not sufficient to execute all planned test cases
Still - as many critical faults should be found as possible
The prioritization rule:
A premature end of testing should still assure the best possible test result at that actual point in time

Entry Criteria - Defining When to Start Testing
Exit Criteria - Defining When to Stop Testing
Test Strategy - Defines the project's testing objectives and the means to achieve them
Determines testing effort and costs
The main goal of the test strategy is to choose the best test approach
Optimizing the relation between costs of testing and costs of defects
Test Approach
Implementation of the test strategy for a specific project
The testing strategy usually involves a combination of test approaches

Preventive approaches
Testers are involved from the beginning:
Test planning and design start as early as possible


Reactive approaches
Testers are involved (too) late and a preventive approach cannot be chosen
Test planning and design starts after the software or system has already been produced