Three Key Pressure‑Testing Questions: Defining Test Points, Getting Expected Metrics, and Crafting Strategies

The author, Da Tian, groups pressure‑testing knowledge into three frequent questions: (1) the rule for extracting test points, (2) how to obtain effective expected metrics (i.e., requirements), and (3) the overall testing strategy.

Single‑scenario load test aims to apply increasing pressure to verify whether the system can sustain load and to capture service capacity and performance. The method uses JMeter on a single machine, starting with 50 concurrent threads, adding 50 threads each minute until reaching 300 threads, and running for a total of 15 minutes. The resulting TPS curve is examined to identify the optimal TPS value.

Mixed‑business scenario test simulates a two‑hour peak period where multiple business flows run concurrently. The goal is to see whether the system continues to respond correctly and whether backend resource usage stays within normal bounds. The test sends requests with a fixed concurrency for each transaction, runs continuously for two hours, and follows the same thread‑ramp pattern (50 → 300 threads, increasing by 50 per minute).

Mixed‑business stability test extends the previous scenario to a long‑duration run (8 + hours). The same fixed‑concurrency approach is used, with the thread count again starting at 50 and increasing by 50 each minute until 300, maintaining the load for the entire period to collect comprehensive performance indicators.

All numeric values (initial threads, increment step, duration, etc.) should be adjusted to match the actual test environment.