Agile practice: Test Strategy

Objective 

Before starting any project , we always try to consider working on certain pointers which will help the team in long go. One of them is a QA Strategy & defining the scope of QA in the project.

Scope

What should be the scope of quality related to sprint, release, UAT, etc. If we work on it before hand during initial phases of the project so that we can get maximum benefit out of it.

In Scope

The Framework can focus on the following types of testing:- 

1.  API Testing
2.  Functional Testing
3.  Sanity Testing
4.  Integration Testing
5.  Regression Testing
6.  Database Testing

The Testing scope

1. Testing all the functionalities to ensure the functional & the business outcome is met
2. Ensure the approx % of test coverage how much QA can achieve.
3. Maintain the test cases in Test Management Tool (JIRA) or (TBD) and sharing it continuously with the stakeholders.

Out Scope

Non functional & functional aspects

1. Performance Testing
2. Load Testing
3. Stress Testing
4. Mobile Testing 
5. Testing on Tablet devices for OS (I.e IOS & Android)
6. Accessibility Testing
7. Testing of disaster recovery and Business Continuity Plan
8. OS versions which we are not going to support
9. Browser versions which we are not going to support

To achieve an overall customer satisfaction rating of “Excellent” and to deliver “First Time Right” bug free application.

Quality Objective

Environments

Name	Description	Data Setup	Test Usage
Development	This environment is local and specific to each developer machine.	configuration scripts	Unit Test
QA	This environment is local and specific to each tester machine.	Through setup scripts.	Functional & non functional Integration Tests
UAT	user acceptance environment	Through configuration setup scripts.	Regression & Integration tests.
pre production	This environment support exploratory testing	Populated with obfuscated production data	Exploratory testing/ Critical Release Verification
Production	Live environment	New instances will contain standard project reference data. Existing instances will have current data migrated into the environment	Production verification testing

environment scope

Testing Tools 

List of tools getting used in the Project:-

Description	Tool	Source	Version
Test Management	Jira	Licensed	Latest
Defect Locking\Tracking	Jira	Licensed	Latest

test management tools

Description	Automation Tools	Source	Version
GUI Functional Testing	Selenium WebDriver	Open-Source	Latest
API Testing	Rest Assured	Open-Source	Latest

automation tools

Test Execution

Where test will execute.

1. Define steps to build the system
2. Define steps to execute automated tests
3. Define those test cases which can not be automated.
4. Define steps to populate environment with reference data
5. Define steps to generate test report/code metrics

Defect Management 

Use relevant defect management system wherein we can define the severity/priority of the bugs.

jira- create bug

Severity	Description
Blocker	Defect causes critical loss of business functionality or a complete loss of service has occurred
Critical	Defect causes major impact to business functionality and there is not an interim workaround available.
Minor	Defect causes minor impact to business functionality and there is an interim workaround available.
Trivial	Defect is cosmetic only and usability is not impacted

Severity

Priority

Severity	Description
High	Shall be taken at most on priority
Medium	Has to be fixed, and can be taken after high priority bugs.
Low	Has to be fixed, and can be later from backlog.

Priority

Browser scope

	Browser Market Share United States Of America	Mobile Browser Market Share in United States Of America	Latest version	Comments/Recommendations
Chrome	47.75%	54.47%	83	Supported: Last 2 versions
Safari	35.26%	38.60%	13.1	Supported: Last 2 versions
Firefox	4.29%	0.73%	78	Supported: Last 2 versions
Edge Legacy	3.07%	0	83	Supported: Last 2 versions/Minimal usage?
IE	2.91%	0	11	Supported: Last 2 versions/Minimal usage?
Samsung Internet	2.29%	4.96%		As per the usage can ignore/keep for on demand basis
Opera	0	0.36%	69	As per the usage can ignore/keep for on demand basis
Android	0	0.27%		As per the usage can ignore/keep for on demand basis

browser matrix

Operating System scope

Paid tool (If any)

Define any paid tool is required for

1. Accessibility testing
2. Cross browser testing – like Sauce labs, browserstack
3. Continuous testing – AWS , Microsoft Azure, etc