AVAILABLE ON ENTERPRISE

Run Stop Criteria

Automatically Stop Load Tests with Event-based Triggers for Improved Test Accuracy and Efficiency

Keep your tests efficient and impactful, every time. With Run Stop Criteria, you can optimize production testing, save time and credits, and automate capacity tests using intelligent thresholds. These safeguards prevent load testing from affecting your production environment, ensuring a seamless customer experience while maintaining flawless performance at every stage.
 
 

Load test Without Impacting Your Production Environment

Don’t let your production environment crash during load testing. Set safeguards with run stop criteria.

Improve Your Testing Efficiency

Stop a test once it is stable and conclusive. This allows other tests in you CI chain to start and saves valuable testing credits.

Improve Your Performance Test Accuracy

Make sure your load tests aren’t negatively affected by the load generator performance by incorporating run stop criteria on your load generator CPU usage.

Create a Run Stop Criteria

Stop Runs When Your App Performance Starts to Degrade

Use the run stop criteria global error ratio or global response time to stop your load test based on your application performance. Some common use cases for these criteria include:

  • Testing in your production environment

  • Automating capacity tests
Feature 1 - Run Stop Criteria

Stop Runs When You Reach the Test Objective

When performance metrics plateau, continuing the test may no longer provide valuable insights. Leverage run stop criteria like global error ratio or global response time to automatically end your load test once performance has stabilized. This helps you:

  • Meet your testing objectives and move on to the next test in the pipeline

  • Conserve testing credits once your goals are achieved
Feature 2 - Run Stop Criteria

Automatically Stop Runs Producing Inaccurate Results

Stressed load generators can lead to confusing or erroneous load test results. Prevent this with a load generator CPU usage run stop.

  • Example: Stop my run when the load generator mean CPU usage is over 90% for the last 30 seconds.

  • The criteria is measured as a mean CPU usage across all deployed load generators.

  • Easily access logs for stopped runs to see the stop trigger and actual measured value.
Feature 3 - Run Stop Criteria

Start testing now!

Test Gatling Enterprise for free! No credit card is required.

Dive into our other features