Unit 3: Test Management
CO3 : Prepare test plan for an application.
Test Plan
• A document describing the scope, approach, resources and schedule of intended test
activities. It identifies amongst others test items, the features to be tested, the testing
tasks, who will do each task, degree of tester independence, the test environment, the test
design techniques and entry and exit criteria to be used, and the rationale for their
choice, and any risks requiring contingency planning. It is a record of the test planning
process.
Steps for preparing a test plan
• Analyze the product (learn product thoroughly)
• Develop test strategy -define scope of testing ,risk and issues
• Define objective of test
• Define test criteria
• Planning the resources
• Plan test environment
• Schedule and cost
• Test deliverables
Test deliverables includes
Scope
Methodology
Requirements
Criteria for pass-fail
Schedule
TEST PLAN TYPES
• Master Test Plan: A single high-level test plan for a project/product that unifies all other
test plans.
,Unit 3: Test Management
, Unit 3: Test Management
• Testing Level Specific Test Plans :Plans for each level of testing.
– Unit Test Plan
– Integration Test Plan
– System Test Plan
– Acceptance Test Plan
• Testing Type Specific Test Plans: Plans for major types of testing like Performance
Test Plan and Security Test Plan.
TEST PLAN GUIDELINES
• Make the plan concise. Avoid redundancy and superfluousness. If you think you do
not need a section that has been mentioned in the template above, go ahead and delete
that section in your test plan.
• Be specific. For example, when you specify an operating system as a property of a
test environment, mention the OS Edition/Version as well, not just the OS Name.
• Make use of lists and tables wherever possible. Avoid lengthy paragraphs.
• Have the test plan reviewed a number of times prior to base lining it or sending
it for approval. The quality of your test plan speaks volumes about the quality of the
testing you or your team is going to perform.
• Update the plan as and when necessary. An outdated and unused document stinks and
is worse than not having the document in the first place.
Deciding test approach
• Like any project, the testing also should be driven by a plan. The test plan acts as
the anchor
• For the execution, tracking and reporting of the entire testing project. Activities of test
plan:
1. Scope Management: Deciding what features to be tested and not to be tested.
2. Deciding Test approach /strategy: Which type of testing shall be done like
configuration, integration, localization etc.
3. Setting up criteria for testing: There must be clear entry and exit criteria for different
phases of testing. The test strategies for the various features and combinations
determined how these features and combinations would be tested.
4. Identifying responsibilities, staffing and training needs
5. Identifying resource requirements
CO3 : Prepare test plan for an application.
Test Plan
• A document describing the scope, approach, resources and schedule of intended test
activities. It identifies amongst others test items, the features to be tested, the testing
tasks, who will do each task, degree of tester independence, the test environment, the test
design techniques and entry and exit criteria to be used, and the rationale for their
choice, and any risks requiring contingency planning. It is a record of the test planning
process.
Steps for preparing a test plan
• Analyze the product (learn product thoroughly)
• Develop test strategy -define scope of testing ,risk and issues
• Define objective of test
• Define test criteria
• Planning the resources
• Plan test environment
• Schedule and cost
• Test deliverables
Test deliverables includes
Scope
Methodology
Requirements
Criteria for pass-fail
Schedule
TEST PLAN TYPES
• Master Test Plan: A single high-level test plan for a project/product that unifies all other
test plans.
,Unit 3: Test Management
, Unit 3: Test Management
• Testing Level Specific Test Plans :Plans for each level of testing.
– Unit Test Plan
– Integration Test Plan
– System Test Plan
– Acceptance Test Plan
• Testing Type Specific Test Plans: Plans for major types of testing like Performance
Test Plan and Security Test Plan.
TEST PLAN GUIDELINES
• Make the plan concise. Avoid redundancy and superfluousness. If you think you do
not need a section that has been mentioned in the template above, go ahead and delete
that section in your test plan.
• Be specific. For example, when you specify an operating system as a property of a
test environment, mention the OS Edition/Version as well, not just the OS Name.
• Make use of lists and tables wherever possible. Avoid lengthy paragraphs.
• Have the test plan reviewed a number of times prior to base lining it or sending
it for approval. The quality of your test plan speaks volumes about the quality of the
testing you or your team is going to perform.
• Update the plan as and when necessary. An outdated and unused document stinks and
is worse than not having the document in the first place.
Deciding test approach
• Like any project, the testing also should be driven by a plan. The test plan acts as
the anchor
• For the execution, tracking and reporting of the entire testing project. Activities of test
plan:
1. Scope Management: Deciding what features to be tested and not to be tested.
2. Deciding Test approach /strategy: Which type of testing shall be done like
configuration, integration, localization etc.
3. Setting up criteria for testing: There must be clear entry and exit criteria for different
phases of testing. The test strategies for the various features and combinations
determined how these features and combinations would be tested.
4. Identifying responsibilities, staffing and training needs
5. Identifying resource requirements
