Pressure Testing
Pressure Testing
Simulate 10 to 1,000 concurrent users hitting your app simultaneously to surface race conditions, deadlocks, and performance degradation.
How it works
Pressure testing spins up multiple browser sessions concurrently, each going through the full auth flow. This surfaces race conditions, database deadlocks, rate limiting issues, and performance degradation under load.
Parameters
| Parameter | Type | Description |
|---|---|---|
| concurrentUsers | number | Number of simultaneous sessions: 10, 50, 100, 250, 500, 1000 |
| duration | string | Test duration: 1 min, 5 min, 15 min, 30 min |
| rampUp | string | How sessions start: 'instant' (all at once) or 'gradual' (staggered) |
Pressure test config example
json
{
"test_type": "pressure",
"url": "https://yourapp.com",
"config": {
"concurrentUsers": 100,
"duration": "5 min",
"rampUp": "gradual"
}
}What it catches
Race conditions
Two users creating the same resource at the same time -- duplicate records, stale reads, or crashes.
Database deadlocks
Concurrent writes locking each other out. The hippo reports which sessions stalled.
Rate limiting
Verifies that rate limits trigger correctly and return proper error codes (429).
Performance degradation
Response times that increase as concurrency grows -- the report shows p50/p95/p99 latencies.