jmeter-plugins.org
Every load test needs some sexy features!
AutoStopAutoStop used when you want to stop test on some runtime criteria. Currently 6 criteria available: average response time, average latency, error rate, response time percentile, relative window percentile degradation and error count. This criteria are used in OR logic, the component will ask JMeter to stop test if one of the criteria has been met. After 5 tries of "shutdown test" component will switch to more insistent "stop test", after 5 more it will try to "stop NOW". On initiating "shutdown test" AutoStop will create environment variable "auto_stopped" = "true" which can be checked later in order to take additional actions on test failure (e.g. send alert).
AutoStop on Response Time/LatencyThere is combo-box switching which result parameter to use in conditions: response time or latency. Test will be stopped only if specified response time/latency exceeded for sequentially N seconds. To disable auto-stop on time criteria, just set time value to zero. AutoStop on Error RateError rate specified in percent. Rate can be float number. Test will be stopped only if specified error rate exceeded for sequentially N seconds. To disable auto-stop on rate criteria, just set error rate to zero. AutoStop on Percentile Response TimePercentile rank specified as a number, e.g. 90 for P90; the threshold is specified in milliseconds. Test will be stopped only if specified percentile response time exceeded for sequentially N seconds. AutoStop on Relative Window Percentile DegradationCompares a response time percentile across two adjacent tumbling windows. Test will be stopped if the current window's percentile grew by more than the specified percentage compared to the previous window. AutoStop on Error CountError count limit within a fixed time window (tumbling window, not sustained). Test will be stopped if the specified error count is exceeded within N seconds. ExamplesExample AutoStop on Response Time JMX Example AutoStop on Error Rate JMX |
