Skip to main content
srperf
Space Cadet
Aug 13, 2025 9:24 AM UTC

What other types of performance testing can you name that are not automated load testing?

Answer Leandro’s Question for a chance to win a ShiftSync Giftbox
 

 

21 replies

Ensign
Aug 13, 2025 2:17 PM UTC

Endurance, Stress, Spike, 2 tier component testing e.g. database, Redis, Solr, NBus endpoints etc.

Space Cadet
Aug 13, 2025 2:22 PM UTC

Best Case test, Load test, Stress test, Volume test, Endurance test, Spike Test

Ensign
Aug 13, 2025 2:22 PM UTC

Volume Testing, Concurrency Testing,, Scalibility Testing

Space Cadet
Aug 13, 2025 2:25 PM UTC

Stress Testing, Soak / Endurance Testing, Spike Testing, Scalability Testing, Volume Testing, Latency Testing, Capacity Testing, Baseline / Benchmark Testing, Configuration Testing, Manual Exploratory Performance Observation

Space Cadet
Aug 13, 2025 2:26 PM UTC

Manual performance test -- manually uploads large files and notes system lag, CPU usage, or slow database queries. concurrent hits of some payload manually by multiple users causing the failure or spiking or behave weird. 

Ensign
Aug 13, 2025 2:31 PM UTC

Soak / Endurance Testing (Manual Monitoring Approach)
Spike Testing
Configuration & Scalability Testing
Failover & Resilience Testing
Real-User Performance Monitoring (RUM)
Performance Profiling
Capacity Testing
UI Profiling

Space Cadet
Aug 13, 2025 2:31 PM UTC

Stress Testing,Spike Testing,Endurance Testing  and Scalability/Capacity Testing, peak testing etc

Space Cadet
Aug 13, 2025 2:32 PM UTC

Load test not performa test..

Space Cadet
Aug 13, 2025 2:34 PM UTC

Endurance or Soak, Stress, Web Performance, Observability, Backend, Mobile, Prod Performance, Synthetic. 

Ensign
Aug 13, 2025 2:35 PM UTC
  • Soak (prolonged time periods under steady load)
  • Concurrency (multiple, and increasing, simultaneous API calls or users through UI)
  • Stress (high load to observe behavior are high loads)
  • Capacity (evaluate / determine limits - similar but different than stress)
  • Failure testing (fail / recover / switchover under load)
  • Benchmark evaluation (comparison of build / versions or competitors)
  • Spike (rapid drop-off or increase in load - square wave, sawtooth, spikes)