Most JMeter test plans I’ve inherited share a common shape. Two hundred threads, one ramp-up, a flat plateau, and a results table that says “p95 was 480ms.” Somebody declares the system performant, the test plan goes into a Confluence page, and nobody runs it again until the next major release.
The problem is that the test doesn’t model anything. The traffic shape is wrong, the user behavior is wrong, the data volumes are wrong, and the security controls aren’t being exercised. The system passes the test and then fails in production at peak load because production traffic doesn’t look like the test.
This article has been indexed from DZone Security Zone
Read the original article: