Test Strategy VS Test Plan

a.Test strategy is master testplan.It will talk about the 
Budget,Timelines,objective.
b.What is the technical architecture of the 
application/product ?
c.What are the various types of testing to be performed ?
d.What is the development methodology for the 
application/product ?
e.What should be tested and how ? What should not be tested 
and why ?
f.Should the entire product/application be tested as a 
whole or run tests only on a certain part of it? 
g.As new components are added to a large system, should the 
tests be re-run which have already conducted?
h.What are the tools that can be used? 
i.What should the resources be trained on?
j.When should the end-user be involved?
	
And testplan is written for each type of testing,Like 
system testplan,UAT plan,Performance testplan,
It is more specific to type of testing.
The test plan will answer the following questions:
What is being tested?  
1. What are pass/fail criteria? 
2. When will each test occur? 
3. What hardware and software environment is required? 
4. What features must be tested? 
5. What features will not be tested? 
6. What are the responsibilities of individuals and 
organizations involved in the project? 
7. Identify the various modules and decide which 
modules/functionalities will be tested. Clearly mention 
which items are out-of-scope for testing
8. List down the priority of testable items (conflict-
resolution between the various players is of importance)









Another Blog:

20-Oct-2007 - Test Strategy Vs Test Plan

A test strategy is a statement of the overall approach to testing, identifying what levels of testing

are to be applied and the methods, techniques and tools to be used. A test strategy should ideally

be organization wide, being applicable to all of organizations software developments.

 

Developing a test strategy, which efficiently meets the needs of an organization, is critical to the

success of software development within the organization. The application of a test strategy to a

software development project should be detailed in the projects software quality plan.

 

The next stage of test design, which is the first stage within a software development project, is the

development of a test plan. A test plan states what the items to be tested are, at what level they

will be tested, what sequence they are to be tested in, how the test strategy will be applied to the

testing of each item, and describes the test environment.

 

A test plan may be project wide, or may in fact be a hierarchy of plans relating to the various levels

of specification and testing:

 

• An Acceptance Test Plan, describing the plan for acceptance testing of the software. This would usually be published as a separate document, but might be published with the system test plan as a single document.
• A System Test Plan, describing the plan for system integration and testing. This would also usually be published as a separate document, but might be published with the acceptance test plan.
• A Software Integration Test Plan, describing the plan for integration of testes software components. This may form part of the Architectural Design Specification.
• Unit Test Plan(s), describing the plans for testing of individual units of software. These may form part of the Detailed Design Specifications.

The objective of each test plan is to provide a plan for verification, by testing the software, that the

software produced fulfils the requirements or design statements of the appropriate software

specification. In the case of acceptance testing and system testing, this means the Requirements

Specification.