Test Strategy - javatpoint
In this section, we are going to understand the test strategy documentation, which is an integral part of testing documentation.
And we also learn about features of test strategy, components of test strategy, types of test strategies, and different testing activities, which include the test strategy document.
A high-level document is used to validate the test types or levels to be executed for the product and specify the Software Development Life Cycle's testing approach is known as Test strategy document.
Once the test strategy has been written, we cannot modify it, and it is approved by the Project Manager, development team.
The test strategy also specifies the following details, which are necessary while we write the test document:
In other words, we can say that it is a document, which expresses how we go about testing the product. And the approaches can be created with the help of following aspects:
We can write the test strategy based on development design documents.
The development design document includes the following documents:
The primary objective of writing the test strategy is to make sure that all purposes are covered entirely and understood by all stakeholders, we should systematically create a test strategy.
Furthermore, a test strategy objective is to support various quality assurance stockholders in respect of planning of resources, language, test and integration levels, traceability, roles and responsibilities, etc.
In SDLC (Software Development Life Cycle), the test strategy document plays an important role. It includes various significant aspects, such as who will implement the testing, what will be tested, how it will be succeeded, and what risks and incidents will be are related to it.
Some of the additional characteristics of the Test Strategy document are as follows:
We understand that the test strategy document is made during the requirements phase and after the requirements have been listed.
Like other testing documents, the test strategy document also includes various components, such as:
Let's see them one by one for our better understanding:
6. Risk Analysis
Here, we are discussing some of the significant types of test strategies document:
Let's understand them one by one in detail:
We can combine the two or more strategies as per the needs of the product and organization's requirements. And it is not necessary to use any one of the above listed test strategies for any testing project.
The selection of the test strategy may depend on the below aspects:
The final document of the test strategy contains important details about the following factors:
After understanding the test strategy document, at last, we can say that the test strategy document provides a vibrant vision of what the test team will do for the whole project.
The test strategy document could prepare only those who have good experience in the product domain because the test strategy document will drive the entire team.
And it cannot be modified or changed in the complete project life cycle as it is a static document.
Before any testing activities begin, the Test strategy document can distribute to the entire testing team.
If the test strategy document is written correctly, it will develop a high-quality system and expand the complete testing process.
SoapUI
RPA
Manual T.
Cucumber
Appium
PostgreSQL
Solr
MongoDB
Gimp
Verilog
Teradata
PhoneGap
Aptitude
Reasoning
Verbal A.
Interview
Company
AI
AWS
Selenium
Cloud
Hadoop
ReactJS
D. Science
Angular 7
Blockchain
Git
ML
DevOps
DBMS
DS
DAA
OS
C. Network
Compiler D.
COA
D. Math.
E. Hacking
C. Graphics
Software E.
Web Tech.
Cyber Sec.
Automata
C
C++
Java
.Net
Python
Programs
Control S.
Data Mining
Hindi100
Lyricsia
Website Development
Android Development
Website Designing
Digital Marketing
Summer Training
Industrial Training
College Campus Training
Address: G-13, 2nd Floor, Sec-3
Noida, UP, 201301, India
Contact No: 0120-4256464, 9990449935
© Copyright 2011-2021 www.javatpoint.com. All rights reserved. Developed by JavaTpoint.
