Availability Testing

• tests whether a system can produce its services during expected or unexpected events
• frequently used when rolling out a new application release, when performing a backup, when testing what happens when the network is down or when simulating disaster recovery to ensure a major service disruption will not occur

Black-Box Testing

• used by analysts and users
• inputs and outputs of functions are known, but internal code structure is irrelevant

Capacity Testing

• determines the number of users and/or transactions a system will support while meeting performance goals

Endurance (Soak) Testing

• determines if the application can withstand the expected load
• memory operation is scrutinized to detect potential leaks
• helps to prevent performance degradation
• safeguards that the throughput and/or response times after continuous activity are comparable to or exceed those at the start of the test

Fail-Over Testing

• validates redundancy processes during system load execution

Feedback Based Testing

• tester uses initial test results to pilot future exploration

Freestyle Testing

• does not utilize any rules or patterns
• application feature investigation in any order
• can use any input without concern about which features may or may not have been included

Load Testing

• designed to exercise the system in terms of number of users
• establishes response time for time sensitive transactions and business processes  
• verifies application actions under normal and peak load environments
• evaluates application capability to function under load; measures transaction pass/fail/error rates
• confirms results are within documented expectations (Service Level Agreements)

Network Sensitivity Testing

• concentrates on Wide Area Network (WAN) restrictions and network activity
• may be exploited to calculate the WAN segment or traffic profile effect on bandwidth dependent applications

Performance Testing

• methodical analysis to determine or validate the speed, scalability and/or stability features of a product under a specific test
• supports or invalidates whether performance-related activities (for example, testing and tuning) meet the performance objectives
• includes assessment of response times, throughput and resource-utilization levels