Commencez. C'est gratuit
ou s'inscrire avec votre adresse courriel
Rocket clouds
TESTING par Mind Map: TESTING

1. Fundamentals of testing

1.1. TESTING NECESSARY

1.1.1. Software systems context

1.1.1.1. Error (Mistake)

1.1.1.2. Defect (bug, fault)

1.1.1.3. Failure

1.2. WHAT IS TESTING

1.2.1. not debugging

1.2.2. not fix defects

1.3. CODE OF ETHICS

1.4. FUNDAMENTAL TEST PROCESS

1.4.1. Test approach

1.4.2. Test execution

1.5. THE PSYCHOLOGY OF TESTING

1.5.1. test policy

1.5.2. independence of testing

1.5.3. error guessing

1.6. SEVEN TESTING PRINCIPLES

1.6.1. Exhaustive testing is impossible

1.6.2. Testing is context dependent

1.6.3. Defect clustering

1.6.4. Early testing

1.6.5. Absence-of-errors fallacy

1.6.6. Testing show presence of defects

1.6.7. Pesticide paradox

2. Testing throughout the software life cycle

2.1. V-model

2.1.1. performance

2.1.2. Test level

2.1.3. Integration

2.1.4. commercial off-the-shelf (COTS) software

2.2. TEST LEVELS

2.2.1. Component testing

2.2.2. Integration testing

2.2.3. System testing

2.2.4. Acceptance testing

2.3. TEST TYPES

2.3.1. Testing of function (functional testing)

2.3.2. Testing of software product characteristics (non-functional testing)

2.3.3. Testing of software structure/architecture (structural testing

2.3.4. Testing related to changes (confirmation and regression testing)

2.4. MAINTENANCE TESTING

2.4.1. Impact analysis and regression testing

2.4.2. Triggers for maintenance testing

3. Static techniques

3.1. Dynamic

3.1.1. Behavioural

3.1.1.1. Non-functional

3.1.1.1.1. Usability

3.1.1.1.2. Performance

3.1.1.2. Functional

3.1.1.2.1. Random

3.1.1.2.2. Boundary Value Analysis

3.1.1.2.3. State Transition

3.1.1.2.4. Equivalence Partitioning

3.1.1.2.5. Cause-Effect Graphing

3.1.2. Structural

3.1.2.1. Control Flow

3.1.2.2. Data Flow

3.1.2.2.1. Symbolic Execution

3.1.2.2.2. Definition-Use

3.2. Static

3.2.1. Static Analysis

3.2.2. Walkthroughs

3.2.3. Reviews

3.2.4. Inspection

3.2.5. Desk-checking

4. Test design techniques

4.1. THE TEST DEVELOPMENT PROCESS

4.1.1. test case specification

4.1.2. test design specification

4.1.3. test design technique

4.1.4. test execution schedule

4.1.5. horizontal traceability

4.1.6. vertical traceability

4.1.7. traceability

4.2. CATEGORIES OF TEST DESIGN TECHNIQUES

4.2.1. experience-based test design technique

4.2.2. specification-based test design technique

4.2.3. structure-based

4.2.4. test design technique

4.3. SPECIFICATION-BASED OR BLACK-BOX TECHNIQUES

4.3.1. boundary value analysis

4.3.1.1. boundary value

4.3.1.2. equivalence partition

4.3.1.3. equivalence partitioning

4.3.2. decision table testing

4.3.2.1. decision table

4.3.3. state transition testing

4.3.3.1. state diagram

4.3.3.2. state table

4.3.4. use case testing

4.4. STRUCTURE-BASED OR WHITE-BOX TECHNIQUES

4.4.1. branch coverage

4.4.2. code coverage

4.4.3. coverage, decision coverage

4.4.4. statement coverage

4.4.5. test coverage

4.5. EXPERIENCE-BASED TECHNIQUES

4.5.1. attack

4.5.2. exploratory testing

4.5.3. fault attack

5. Test management

5.1. TEST ORGANIZATION

5.1.1. tester

5.1.2. test leader

5.1.3. test manager

5.1.4. test management

5.2. TEST PLANNING AND ESTIMATION

5.2.1. reasons

5.2.2. relate to projects, test levels,..

5.3. TEST PROGRESS MONITORING AND CONTROL

5.3.1. defect density

5.3.2. failure rate

5.4. CONFIGURATION MANAGEMENT

5.4.1. configuration control

5.4.2. configuration management

5.4.3. version control

5.5. RISK AND TESTING

5.5.1. product risk

5.5.2. project risk

5.5.3. risk-based testing

5.6. INCIDENT MANAGEMENT

5.6.1. defect detection percentage

5.6.2. defect report

5.6.3. incident logging

5.6.4. incident management

5.6.5. incident report

5.6.6. priority

5.6.7. root cause

5.6.8. severity