Get Started. It's Free
or sign up with your email address
Rocket clouds
Software Testing by Mind Map: Software Testing

1. Requirement Analysis

1.1. contains complete description about how the system is expected to perform

1.2. try to understand what the target application is going to be like

2. Planning Creation

2.1. What

2.1.1. Test level

2.1.1.1. Integration test

2.1.1.2. Unit test

2.1.1.3. System test

2.1.1.4. Acceptance test

2.1.2. Test type

2.1.2.1. Function

2.1.2.2. Non-function

2.1.2.2.1. Recovery

2.1.2.2.2. GUI

2.1.2.2.3. Recovery

2.1.2.2.4. GUI

2.1.2.2.5. Performance

2.1.2.2.6. Usabilty

2.1.2.2.7. Security

2.1.2.2.8. ...

2.2. When: Milestones

2.3. How to test

2.3.1. Automation

2.3.2. Manual

2.3.3. Methodologies

2.3.3.1. White-box testing

2.3.3.1.1. Statement coverage

2.3.3.1.2. Condition coverage

2.3.3.1.3. Branch coverage

2.3.3.1.4. Path coverage

2.3.3.1.5. ...

2.3.3.2. Black-box testing

2.3.3.2.1. Boundary testing

2.3.3.2.2. State transiton

2.3.3.2.3. Decision table

2.3.3.2.4. equivalent partition

2.3.3.2.5. Error guesting

2.3.3.2.6. ...

2.4. Where: Enviroment to test

2.5. Who test

2.5.1. Resource planning

2.5.2. Determine roles and responsibilities.

3. Enviroment Preparation

3.1. Activities

3.1.1. Understand the required architecture, environment set-up

3.1.2. Prepare hardware and software requirement list for the Test Environment.

3.1.3. Setup test Environment and test data

3.1.4. Perform smoke test on the build

3.1.5. Activities

3.1.5.1. Understand the required architecture, environment set-up

3.1.5.2. Prepare hardware and software requirement list for the Test Environment.

3.1.5.3. Setup test Environment and test data

3.1.5.4. Perform smoke test on the build

3.2. Deliverables

3.2.1. Environment ready with test data set up

3.2.2. Smoke Test Results

4. Execution

4.1. Activities

4.1.1. Execute tests as per plan

4.1.2. Document test results, and log defects for failed cases

4.1.3. Map defects to test cases in RTM

4.1.4. Retest the Defect fixes

4.1.5. Track the defects to closure

4.1.6. Activities

4.1.6.1. Execute tests as per plan

4.1.6.2. Document test results, and log defects for failed cases

4.1.6.3. Map defects to test cases in RTM

4.1.6.4. Retest the Defect fixes

4.1.6.5. Track the defects to closure

4.2. Deliverables

4.2.1. Completed RTM with the execution status

4.2.2. Test cases updated with results

5. Report

5.1. A summary of test activities and final test results

5.2. An assessment of how well the Testing is performed

6. Closure

6.1. Activities

6.1.1. Evaluate cycle completion criteria based on Time, Test coverage, Cost,Software, Critical Business Objectives, Quality

6.1.2. Prepare test metrics based on the above parameters.

6.1.3. Document the learning out of the project

6.1.4. Prepare Test closure report

6.1.5. Qualitative and quantitative reporting of quality of the work product to the customer.

6.1.6. Test result analysis to find out the defect distribution by type and severity.

6.2. Deliverables

6.2.1. Test Closure report

6.2.2. Test metrics

7. Design

7.1. Activities

7.1.1. Create test cases, automation scripts (if applicable)

7.1.2. Review and baseline test cases and scripts

7.1.3. Create test data (If Test Environment is available)

7.2. Deliverables

7.2.1. Test scenario

7.2.2. Test cases

7.2.3. Test data

7.2.4. Test script