The document outlines the processes of test strategy and planning in software testing, emphasizing the distinction between a test strategy document and a test plan document. It details the components of each document, including objectives, scope, resources, and risk management, while providing techniques for estimating testing efforts. Overall, it highlights the importance of thorough documentation and clear communication for effective quality assurance.

1. Quality Assurance /
Software Testing Training
Test Strategy and Planning

2. Page 2Classification: Restricted
Agenda
• Test Strategy and Planning
• Test Strategy Document
• Test Planning
• Test Estimation Techniques

3. Page 3Classification: Restricted
Test Strategy and Planning
Test Strategy
A test strategy is an outline that describes the testing approach of the
software development cycle This document defines “Software Testing
Approach” to achieve testing objectives. The Test Strategy is normally
Derived from the Business Requirement Specification document.
Some companies include the “Test Approach” or “Strategy” inside the Test
Plan, which is fine and it is usually the case for small projects. However, for
larger projects, there is one Test Strategy document and different number of
Test Plans for each phase or level of testing.

4. Page 4Classification: Restricted
Test Strategy Document
• Scope and Objectives
• Business issues
• Roles and responsibilities
• Communication and status reporting
• Test deliverability
• Industry standards to follow
• Test automation and tools
• Testing measurements and metrices
• Risks and mitigation
• Defect reporting and tracking
• Change and configuration management
• Training plan

5. Page 5Classification: Restricted
Test Planning
The Test Plan document on the other hand, is derived from the Product
Description, Software Requirement Specification SRS, or Use Case
Documents.
The Test Plan document is usually prepared by the Test Lead or Test
Manager and the focus of the document is to describe what to test, how to
test, when to test and who will do what test.
Objectives
• To create a set of testing tasks.
• Assign resources to each testing task.
• Estimate completion time for each testing task.
• Document testing standards.

6. Page 6Classification: Restricted
Purpose of preparing a Test Plan
• Validate the acceptability of a software product.
• Help the people outside the test group to understand ‘why’ and ‘how’ of
product validation.
A Test Plan should be
• Thorough enough (Overall coverage of test to be conducted)
• Useful and understandable by the people inside and outside the test
group.

7. Page 7Classification: Restricted
A document that describes the
• Introduction
• Scope
• Approach
• Resources
• Roles and Responsibilities
• Entry and Exit criteria
• Hardware and Software requirement
• Schedule
• Risk and Mitigation
• Tools to be used
• Deliverables
• References
• Annexure

8. Page 8Classification: Restricted
Scope
• The areas to be tested by the QA team.
• Specify the areas which are out of scope (screens,database,
mainframe processes etc).
Test Approach
• Details on how the testing is to be performed.
• Any specific strategy is to be followed for testing (Including CM)
Entry Criteria
• Various steps to be performed before the start of a test i.e. Pre-
requisites.
E.g.
• Timely environment set up
• Starting the web server/app server
• Successful implementation of the latest build etc.
Resources
List of the people involved in the project and their designation etc.

9. Page 9Classification: Restricted
Tasks/Responsibilities
• Tasks to be performed and responsibilities assigned to the various team
members.
Exit Criteria
• Contains tasks like Bringing down the system / server ,Restoring system
to pre-test environment, Database refresh etc.
Schedule / Milestones
• Deals with the final delivery date and the various milestones dates.
Hardware / Software Requirements
• Details of PC’s / servers required to install the application or perform
the testing
• Specific software to get the application running or to connect to the
database etc.

10. Page 10Classification: Restricted
Risks & Mitigation Plans
• List out the possible risks during testing
• Mitigation plans to implement incase the risk actually turns into a
reality.
Tools to be used
• List the testing tools or utilities
Eg.WinRunner, LoadRunner, Test Director, Rational Robot, QTP, JIRA
etc
Deliverables
• Various deliverables due to the client at various points of time i.e.
Daily / weekly / start of the project end of the project etc.
• These include test plans, test procedures, test metric, status reports,
test scripts etc.

11. Page 11Classification: Restricted
References
• Procedures
• Templates (Client specific or otherwise)
• Standards / Guidelines e.g. Qview
• Project related documents (RSD, ADD, FSD etc).
Annexure
• Links to documents which have been / will be used in the course of
testing
Eg. Templates used for reports, test cases etc.
• Referenced documents can also be attached here.
Sign-off
• Mutual agreement between the client and the QA Team.
• Both leads/managers signing their agreement on the Test Plan.

12. Page 12Classification: Restricted
Test Estimation Techniques
Estimating effort for test is one of the major and important tasks in SDLC.
Correct estimation helps in testing the Software with maximum coverage.
This section describes some of the techniques which can be useful during
the estimating of effort for testing.
List of Different Estimation Techniques
• Best guess
• Ad-hoc method
• Experience Based - Analogies and experts
• WBS
• Delphi technique
• Three-point estimation (successive calculation)
• Function points / Test point Analysis

13. Page 13Classification: Restricted
Thank You