top of page
Search

Agile practice: Test Strategy

  • Writer: khyati sehgal
    khyati sehgal
  • Aug 15, 2020
  • 3 min read

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

environment scope

Testing Tools

List of tools getting used in the Project:-

test management tools

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

CriticalDefect 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.TrivialDefect is cosmetic only and usability is not impacted

Severity

Priority

MediumHas 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 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

Comments

bottom of page