TEST STRATEGY

1) What is test strategy document? What it contain in the Test strategy?

Ans. Test Strategy is Organizational Document. which is usually developed by PM or Sr. Tester
It is a testing approach, contains the objective and scope of the project, risks involved in the
project and how to achieve the testing.
It becomes an input to test plan, which will be developed by the test lead.
The overall testing approach for the application-under-test includes stages of testing, completion
criteria, and general testing techniques.
A document that identifies the organization and structure for the strategy, tasks, and in to be used
during test development and execution.
A Test strategy used to project test more likely to find errors made in the first place, more likely to
expose errors so they are more obvious if they’re made, or more likely to detect them errors that
will be made, because every program path can not be tested
Also the strategy document depends on what it is related to if it is software testing all the above
implements

If same you consider the business ,project management and marketing level the strategy differs
here.

Test strategy is defined by the QA manager in the Test Plan of a particular Project. In that project
if we are using Black Box testing techniques. In Black Box Testing there are five types of strategy
like
a) Error Guessing
b) Equivalence Class
c) Cause Effect Graph matrix
d) Boundary Value Analysis
From those strategies tester can select one of them according to the project limitation or time
limitation.
Test strategy is a document which gives us a plan from start to finish.
Test strategy has scope, approach, schedule, test items, features to be tested/not tested, tasks
and contingencies. Scope is the testing portion, approach is the method of conducting the test,
schedule has starting and ending period of time, test items should match requirements.
Contingencies are the backup plans.
I think it is the project level document and depends upon the organization and project.
Test strategy can be created in designing phase. Management get to know what to expect from
testing. Till 2000, test strategy used to be a different document, now it has become a part of the
test plan.

Test strategy: it is exact or good approach to get the good quality of testing on a product or
application. Thus, testing strategy is divided into five main parts namely: scope and objectives,
business issues, approach, roles and responsibilities and status reporting and communication
modes

in detail:

scope and objective: this gives the information about the objective and limitations of the functions.
Business issues: this defines the % of allocation of the resources between developers and test
engineers.
Approach: this is way how to approach (where and when in the sense how also)
roles and responsibilities: this in clear states the roles and responsibilities of the test engineer and
test team to submit the information in time to the tech lead of the team.
Status reporting and communication modes: this regular happens in the software field with the
clients and higher authorities. Such that which project is in which state and how soon we are
going to complete