Scribd
Upload
34 views2 pages

8.test Strategy

The document discusses what a test strategy is and how to write one. A test strategy explains the process for testing an application and includes sections like scope, test approach, environment, tools, and risk analysis. It also provides tips for a test strategy such as including product background, listing features to test, defining the test approach, and describing test documentation and tracking.

Uploaded by

prasad ghate
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
34 views2 pages

8.test Strategy

The document discusses what a test strategy is and how to write one. A test strategy explains the process for testing an application and includes sections like scope, test approach, environment, tools, and risk analysis. It also provides tips for a test strategy such as including product background, listing features to test, defining the test approach, and describing test documentation and tracking.

Uploaded by

prasad ghate
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

What Is A Test Strategy?

Test strategy means “How you are going to test the application?” You need to
mention the exact process/strategy that you are going to follow when you will get
the application for testing.
According to IEEE Standard 829-2008, the Strategy plan is a sub-item of a test
plan.

## Section of test strategy document

1.Scope and Overview


2.Test Approach
3.Test Environment
4.Testing tools
5.Release Control
6.Risk Analysis
7.Review and Approval

## Simple Tips To Write Test Strategy Document

1. Include product background in the test strategy document. In the first paragraph
of your test strategy document answer – Why stakeholders want to develop this
project?This will help to understand and prioritize things quickly.

2. List all important features you are going to test. If you think some features
are not part of this release then mention those features under “Features not to
be tested label.”

3. Write down the test approach for your project. Clearly, mention what types of
testing you are going to conduct?
i.e. Functional testing, UI testing, Integration testing, Load/Stress testing,
Security testing, etc.

4. Answer questions like how you are going to perform functional testing? Manual or
automation testing? Are you going to execute all test cases from your test
management tool?

5. Which bug tracking tool you are going to use? What will be the process when you
will find a new bug?

6. What are your test entry and exit criteria?

7. How will you track your testing progress? What metrics are you going to use for
tracking test completion?

8. Task distribution – Define the roles and responsibilities of each team member.

9. What documents will you produce during and after the testing phase?

10.What risks do you see in Test completion?

## Key Differernces

1.Test Plan is a document that describes the scope, objective and weight on
software testing task whereas Test Strategy describes how testing needs to be done.
2.Test Plan is used at the project level whereas Test Strategy is used at the
organization level.
3.Test Plan has the primary goal of how to test, when to test and who will verify
whereas Test Strategy has the primary goal of what technique to follow and which
module to check.
4.Test Plan can be changed whereas Test Strategy can’t change.
5.Test Plan is carried out by the test manager whereas the Test Strategy is carried
out by the project manager.

You might also like