Get Started. It's Free
or sign up with your email address
Testing (DRAFT) by Mind Map: Testing (DRAFT)

1. Other Terms

1.1. Verification & Validation

1.1.1. Verification

1.1.2. Validation

1.2. QA & QC

1.2.1. Quality Assurance

1.2.2. Quality Control

2. Test Process

2.1. Test Planning

2.1.1. Risks

2.1.1.1. Product Risks

2.1.1.1.1. Quality Risks

2.1.1.2. Project Risks

2.2. Test Monitoring & Control

2.2.1. Test Metrics

2.2.1.1. Product Metrics

2.2.1.2. Process Metrics

2.2.1.3. Project Metrics

2.2.1.4. People Metrics

2.3. Test Analysis

2.3.1. Requirements

2.3.1.1. Business Requirements

2.3.1.1.1. Vision

2.3.1.1.2. Epic

2.3.1.2. User Requirements

2.3.1.2.1. Use Case

2.3.1.2.2. User Story

2.3.1.3. System Requirements

2.3.1.3.1. Software Requirements Specification (SRS)

2.4. Test Design

2.5. Test Implementation

2.6. Test Execution

2.7. Test Completion

3. Test Types

3.1. Functional Testing

3.1.1. Functional Correctness Testing

3.1.2. Functional Appropriateness Testing

3.1.3. Function Completeness Testing

3.2. Non-Functional Testing

3.2.1. Security Testing

3.2.2. Performance Testing

3.2.2.1. Load Testing

3.2.2.2. Stress Testing

3.2.2.3. Spike Testing

3.2.2.4. Endurance Testing

3.2.2.5. Capacity Testing/Volume Testing

3.2.2.6. Scalability Testing

3.2.3. Usability Testing

3.2.4. GUI Testing

3.2.5. Accessibility testing

3.2.6. Installation testing

3.2.7. Localization testing

3.2.8. Internacionalization Testing

3.2.9. Compatibility Testing

3.2.9.1. Cross-Browser Testing

3.2.9.2. Cross-Platform Testing

3.3. Change-relatest Testing

3.3.1. New Feature Testing

3.3.2. Retest/Confirmation Testing

3.3.3. Regression Testing

3.4. White-box Testing

3.4.1. API Testing

3.4.2. Database Testing

3.4.3. Cloud Testing

3.5. Black-box Testing

4. Test Levels

4.1. Unit/Component Testing

4.2. Integration Testing

4.2.1. Component Integration Testing

4.2.2. System-Integration Testing

4.3. System Testing

4.4. Acceptance Testing

4.4.1. User Acceptance Testing (UAT)

4.4.2. Alpha Testing

4.4.3. Beta Testing

4.4.4. Operational acceptance testing

4.4.5. Contractual acceptance testing

4.4.6. Regulatory acceptance testing

5. Test Documentation

5.1. Organization Documentation

5.1.1. Test Policy

5.1.2. Test Strategy

5.1.2.1. Analytical test strategy

5.1.2.2. Consultative test strategy

5.1.2.3. Methodical test strategy

5.1.2.4. Model-based test strategy

5.1.2.5. Process-compliant test strategy

5.1.2.6. Reactive test strategy

5.1.2.7. Regression-averse test strategy

5.1.2.8. Standard-compliant test strategy

5.1.2.9. Test automation strategy

5.2. Management Documentation

5.2.1. Test Plan

5.2.1.1. Level Test Plan

5.2.1.2. Test Type Test Plan

5.2.1.3. Master Test Plan

5.2.2. Test Status/Progress Report

5.2.3. Test Completion/Result Report

5.3. Dynamic Teting Documentation

5.3.1. Test Case

5.3.2. Test Suit

5.3.2.1. Smoke Test

5.3.3. Checklist

5.3.4. Bug/Defect repot

6. Test Techniques

6.1. Black-box Test Techniques

6.1.1. Domain Analysis

6.1.1.1. Equivalence Partitioning

6.1.1.2. Boundary Value Analysis (BVA)

6.1.2. All Pairs Testing/Pairwise

6.1.3. Decision table testing

6.1.4. State transition testing

6.1.5. Cause-Effect Graphing

6.1.6. Use Case Testing

6.1.7. User Story Testing

6.2. White-box Test Techniques

6.2.1. Statement testing and coverage

6.2.2. Decision testing and coverage

6.2.3. The value of statement and decision testing

6.2.4. Path Testing

6.2.5. Multiple Condition Testing

6.2.6. Modified condition/Decidsion Testing

6.3. Experience-based Test Techniques

6.3.1. Error guessing

6.3.2. Exploratory testing

6.3.3. Ad-hoc testing

6.3.4. Checklist-based testing

6.3.5. Defect-Based Test Techniques

6.3.5.1. Defect taxonomies

7. Test Approaches

7.1. Static Testing

7.2. Dynamic Testing

7.3. Risk-Based Testing

7.4. Manual Testing

7.5. Test Automation