📓
Loadium Wiki
  • Welcome to Loadium
  • Getting Started with Loadium
  • Quick Guides
    • Quick Start
    • JMeter Test
    • Locust Test
    • Script Builder
      • Simple HTTP Builder
      • Record&Play
    • Gatling Test
    • WebDriver Test
    • HLS Test
    • Understanding Test Reports
    • Test Execution Fail Reasons
    • File Output
  • ABOUT LOADIUM
    • Features
    • Pricing
    • VUH - Virtual User Hour
  • ACCOUNT
    • Profile & Account
    • Subscription
  • Features
    • Test Report
    • Compare Test
    • Private Location
    • Report PDF Export
  • Test Settings
    • Split CSV
    • Sandbox
    • Multi-Step
    • Geolocation
    • Customize Setup
    • Dedicated IP
    • Send Email
    • DNS Override
    • TPS
    • Network Type
    • Test Scheduling
    • Test Failure Settings
    • JMeter Settings
    • Failure Criteria
    • Flexible Thread Scheduling
  • CONTINUOUS INTEGRATION SUPPORT
    • Azure DevOps Pipeline
    • Jenkins Load Testing with Loadium
  • Integrations
    • Microsoft Teams Integration
    • New Relic Integration
    • AppDynamics Integration
    • TeamCity Integration
  • Jmeter Corner
    • Built-in JMeter Functions
    • How to Install JMeter Plugins
    • Record and Play Load Testing With Jmeter in 5 Steps
    • Websocket with Apache JMeter
    • JMeter Timers
    • Handling Error Messages of JMeter Tests in Loadium
    • Details of Throughput Controller in JMeter (Splitting Threads to Different Requests)
    • How to Add a Varying Number of Parameters in Apache JMeter
    • Local Network Simulation On JMeter
    • Running Load Test with FTP Server
  • Gatling Corner
    • Introduction to Gatling
    • Gatling Recorder
    • Gatling Pros&Cons
  • PUBLIC APIs
    • Get Test Status Service
    • Authentication Service
    • Get Performance Test List Service
    • Start Performance Test Service
Powered by GitBook
On this page
  • How To Use
  • Example

Was this helpful?

  1. Test Settings

Test Failure Settings

What is , How to Use & Things to Pay Attention

PreviousTest SchedulingNextJMeter Settings

Last updated 7 months ago

Was this helpful?

The Failure Criteria feature allows you to set your test's pass/fail criteria for various metrics, such as response time, errors, hits/s, latency, bandwidth, throughput etc.

How To Use

During creating or editing a test, you will find the Test Failure Settings tab.

After clicking the “+” icon, the following screen will appear.

  • Label - Specify here if you want to use this rule on a particular label from your script. It's set to "ALL" (all labels) by default.

  • Key Performance Indicator - Select the specific metric you'd like to apply a rule for. Click the down arrow on the right side of the field to open a drop-down menu and review available metrics to monitor.

  • Condition - The binary comparison operators for this rule, include; "Less than", "Greater than", "Equal to", and "Not Equal to". Click the down arrow on the right side of the field to open a drop-down menu.

  • Threshold - The numeric value you want this rule to apply to.

  • Stop Test - If this box is checked, the test will stop immediately when that criteria fails; otherwise, it will continue running uninterrupted.

Example

Stop testing if the hits.count of all labels is greater than 3.

After saving the Failure Criteria, let's start the test and see the results. The test was stopped because the hits.count of all labels exceeded 3.

On the report screen, we can see the results in the Failure Criteria field.

Enjoy load testing!

If you don't see the answer to your question here, please to let us know! We're always improving our documentation.

Quick Start
JMeter Test
Dedicated IP
Understanding Test Reports
VUH - Virtual User Hour
Features
reach out to us