Performance testing

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

1. BottleNeck

2. Baseline

3. Collect information

3.1. Stakeholders

3.1.1. Decisions

3.2. Types of information

3.2.1. Tuning

3.2.2. Goals and requirements

3.2.3. Hardware/Software configuration

4. Core Activities

4.1. Identify Environment

4.2. Identify Acceptance Criteria

4.3. Plan and Design Tests

4.4. Configure Environment

4.5. Implement Design

4.6. Execute

4.7. Analyze, Report

5. Expectations

5.1. Large data volumes

5.2. High load

5.3. Inexperienced programmers

5.4. Customer requests it

6. Types

6.1. Load Testing

6.1.1. Application server(s) or software

6.1.2. Database server(s)

6.1.3. Network – latency, congestion, etc.

6.1.4. Client-side processing

6.1.5. Load balancing between multiple servers

6.2. Stress testing

6.2.1. Determine breaking points or safe usage limits

6.2.2. to confirm intended specifications are being met

6.2.3. to determine modes of failure (how exactly a system fails)

6.2.4. to test stable operation of a part or system outside standard usage

6.3. Endurance testing

6.4. Spike testing

6.5. Configuration testing

6.6. Isolation testing

7. Performance scenarios selection criteria

7.1. Business critical scenarios

7.2. Mostly accessed scenarios

7.3. Obvious

7.4. Technically risky

7.5. Stakeholders concern