Get Started. It's Free
or sign up with your email address
Test Strategy by Mind Map: Test Strategy

1. Dependencies

1.1. CMS

1.2. CMC

1.3. Masterdata

1.4. CAR

1.5. FDZ

1.6. Prudsys

1.7. FactFinder

1.8. CCR

2. Automated Tests

2.1. Factors to be considered

2.1.1. Risk

2.1.2. How long it takes to run the tests manually

2.1.3. What is the cost of automating the test

2.1.4. How easy are the test cases to automate

2.1.5. How many times is the test expected to run in the project

2.2. Environment Configuration

2.3. Environment Stability

3. Risks

3.1. Identify the most critical areas

3.2. Environment Configuration and Stability

3.3. Mocked Test Data

3.4. Country Skinning

3.5. Coverage

3.6. Accesability and Usability of dependencies

3.7. Application Testability

3.8. Build Merge Issues

3.9. Resource Allocation

4. Testing Processes

4.1. Tooling

4.1.1. Jira Plugin for test cases

4.1.2. Confluence

4.1.3. Jenkins

4.1.4. S4

4.2. Defect Handling

4.3. Methodology

4.3.1. Scrum DOR DOD

4.4. Deliverables

4.4.1. Reports

4.4.2. Templates Test Scenario Defect Story

4.5. Test Environments

4.5.1. Each team should have their own Test Env

4.6. Equipment

4.6.1. Hardware Desktop Tablet Virtual Machines Mobile Devices

4.6.2. Software Browsers Coverage Automation Tools

5. Types of testing

5.1. Unit Testing

5.1.1. Defined and Done by the Development Team

5.2. Functional Testing

5.2.1. Done in the sprint

5.2.2. Cross-browser Testing included here and also in the sprint

5.3. System Testing

5.3.1. Including end-to-end

5.4. Regression Testing

5.4.1. Done after each sprint is ended, before goLive with the previous sprint build

5.4.2. Integration of the functionalities tested in the sprint should be covered here.

5.4.3. Automated tests ran

5.5. Smoke Testing

5.5.1. Using the automated tests

5.6. Acceptance Testing

5.6.1. Done by the countries

5.7. Performance Testing

5.7.1. Done by Operations Team

5.8. Security Testing

5.8.1. Dedicated resource

6. Scope and Objectives

6.1. Improve the Quality of the application

6.2. Improve the testability of the Application

6.3. Define the test process

7. Roles and Responsibilities

7.1. Tester

7.1.1. Involved in all Scrum Processes

7.1.2. Design and execute Tests

7.1.3. Raise any risks and concerns to the Scrum team

7.1.4. Create or assist in creating the Test Strategy/Plan

7.1.5. Reports defects and test results to Stakeholders

7.1.6. Provide inputs to the team in order to improve the test process

7.1.7. Works closely with the Dev Team in order to provide good quality

7.2. Automation Tester

7.2.1. Design and implement Automated Tests

7.2.2. Decide Functionalities to be automated

7.2.3. Maintain the existing Automated Tests

7.2.4. Configures the tools used to Automate

7.2.5. Run the Automated Tests and evaluates results

8. Functionalities Structure

8.1. <- Click on the arrow in the left (MSITS NETWORK)