# Test Failure Settings

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.

![](/files/CknC2A2LDgqTZfNifjwQ)

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

![](/files/4Xr1A5vqKguIxboqqcTN)

* **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.

![](/files/jOFSXLz8u5oDbwudxukL)

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.

![](/files/-M_tMjBXfJ27c4X_-lVC)

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

![](/files/-M_tMxg1FGcWmX7avbL6)

Enjoy load testing!

{% content-ref url="/pages/-MUSAoEB7WKUP6OKgxHU" %}
[Quick Start](/creating-your-first-test.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MUSAunBwe2J09CIl1hu" %}
[JMeter Test](/create-test/jmeter-test.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MUSDlUqfBVdT1lh-1Bf" %}
[Dedicated IP old ui](/test-settings/what-is-dedicated-ip-old.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MUSF4HtwcKhwIZM3EdC" %}
[Understanding Test Reports](/create-test/understansing-test-reports.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MUT64e7K16MOCUe5UD3" %}
[VUH - Virtual User Hour](/about-loadium/vuh-virtual-user-hour.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MUT6iOSA6kWcHdMz1am" %}
[Features](/about-loadium/features.md)
{% endcontent-ref %}

If you don't see the answer to your question here, please [reach out to us](https://loadium.com/contact-us/) to let us know! We're always improving our documentation.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.loadium.com/test-settings/test-failure-settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.