> For the complete documentation index, see [llms.txt](https://docs.testmace.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testmace.com/node-types/assertion-node/in-range.md).

# In range

{% hint style="warning" %}
The feature is available for [paid TestMace subscribers](https://testmace.com/pricing/) only.
{% endhint %}

The **In range assertion** interface is as follows:

![](/files/-M4O7lT6do2HwiYRhNVu)

This assertion type is used to check if a current value is within a range. In the `Expected value type` field you should specify the type of values you want to compare (strings or numbers).

In the field labeled as `Expected value` you can see the fields for defining upper and lower bounds of the range and two buttons to specify whether the bounds should be inclusive or not.

For instance, all possible ranges for the values 0 and 10 are:

* \[ 0 \~ 10 ] - a range from 0 to 10, both bounds are inclusive.
* \[ 0 \~ 10 ) - a range from 0 to 10, the upper bound is exclusive.
* ( 0 \~ 10 ] - a range from 0 to 10, the lower bound is exclusive.
* ( 0 \~ 10 ) - a range from 0 to 10, both bounds are exclusive.

{% hint style="info" %}
Note that you can use strings as compared values. In this case, comparison with range bounds is performed symbol by symbol in alphabetical order.
{% endhint %}

The `Use negative statement` flag is used for getting the opposite result, i.e. the current value shouldn't exist in the specified range.

### Error Fixing

The error fixing algorithm depends on the `Use negative statement` flag's state:

* false - sets a \[current \~ current] range
* true - sets a (current \~ current) range


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.testmace.com/node-types/assertion-node/in-range.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.