TEST STRATEGY

TEST STRATEGY: A test strategy is a guideline to be followed to achieve the test objective and execution of test types mentioned in the testing plan.

-------------------------------------------------------------------------------------------------------------------

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.
Test Plan is used at the project level whereas Test Strategy is used at the organization level.
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.
Test Plan can be changed whereas Test Strategy can’t change.
Test Plan is carried out by the test manager whereas the Test Strategy is carried out by the project manager.

------------------------------------------------------------------------------------------------------------------

Following  details can be added in the Test strategy document but it always varies from organization to organization:

             1.        Introduction………………………………#

1.1   About Client………………………….#

1.2   Project details……………………….#

1.3   Objective……………………………….#

1.4   Testing Types………………………..#

1.5   Testing scope…………………………#

1.6   In scope………………………………...#

1.7   Out of scope

1.8   Assumption & Constraints

1.9   Effort assumptions

 

2.        Testing approach…………………….#

2.1   Approach model

2.2   Approach & procedures

2.3   Entry criteria

2.4   Exit criteria

2.5   Testing Iterations

2.6   Test data

2.7   Exit criteria

 

3.        Testing environment……………………#

 

4.        Communication management………#

4.1   Escalation model & matrix

 

5.        Risk, Contingency & Mitigation……#

 

6.        Testing schedule…………………………#

 

7.        Signoff process……………………………#

 

8.        Defect management……………………#

8.1   Defect tool

8.2   Defect review

 

9.        Review meetings………………………..#

9.1   Daily review

9.2   Weekly review

9.3   Monthly review

 

10.     Defect classification………………………#

 

11.     Test deliverables……………………………#

 

12.     Measurement & Tracking metrics…#

 

13.     Closing plan………………………………….#

 

14.     References……………………………………#

 

15.     Definitions & Acronyms……………….#

-------------------------------------------------------------------------------------------------------------------------------------

Document modifications can be tracked by using following table in first page:

Sr. No.	Version	Version Date	Created/ Updated By	Date of Review	Reviewed By	Approved By	Section (s) Changed	Description of Change
1	1.0	14/08/2021	Amit	15/08/2021	Sumit	Lalit		Final Draft
2
3

-------------------------------------------------------------------------------------------------------------------------------------

1.3 Objective

 The objective of this document is to:

·       Defining the types of testing to be performed and testing processes to be followed for the project

·       Describing the test environment requirements

·       Describing the test approach undertaken to achieve the project objectives

·       Defining responsibilities of each party involved

·       Ensuring that all requirements for testing are addressed

·       Ensuring adequate test coverage and satisfaction of the test exit criteria

 1.4    Test Types

 

Test Type	Description
Positive Functional Testing	·       Testing for all valid functionalities and business activities and processes in order to have confidence that system meets the business requirements.
Negative Functional Testing	·       Looking for faults is the most effective approach to testing. In order to have confidence in the quality of software it is necessary to try to break it.
Usability Testing	·       To check for easy navigation of the application ·       To verify that all objects and characteristics like menus, size, positions conform to requirements.
Interoperability	·       Interoperability testing means testing the software to check if it can inter-operate with other software component, software’s or systems. ·       The ability of two or more systems or components to exchange information and to use the information that has been exchanged.
Performance testing	·       Measuring the response time of all the actions under different circumstances
Compatibility	·       Compatibility testing is a part of functional testing conducted on different browsers to ensure the compatibility of the application/website on cross-browsers.
Automation testing	·       Automating the stable functionality to perform regression in fast and efficient manner.

 

1.5 Test Scope:

         The testing scope for project is as following:

           1. Preparation of Test Suite considering of Business Function, Process and Scenarios

           2. Writing detailed Test Cases and Executing Test Cases:

           3. Comprehensive 100% Test Case Execution on latest version of browsers.

           4. Defect retesting

TEST APPROACH:

1) LOFT - Linear on the fly (Used where revamping is done)

2) FEATURE BASED DELIVERY APPROACH:

PreProd (Stage) is deployed when some meaningful piece of code(feature) is implemented and ready to be merged to the production branch. POs will decide on when they want the feature to be delivered to Prod. All the features are deployed in OFF state and will not be enabled until MVP is delivered in full and final Sign-Off is given. 
-Sooner feedback from UAT/BAT. 
 

Pros: 

-Easier Production rollout process in the end;

Cons: 

-Team will need to focus on stabilization and UAT/BAT support of each drop, which can slow down overall MVP implementation; 

-West needs to align with East SRE deployments schedule in the early stages and minimize the risk of impacting SRE releases during feature deliveries.