> For the complete documentation index, see [llms.txt](https://docs.irs.systems/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.irs.systems/ltt/documentation/ltt-gui-manual/teststand/limittests.md).

# Limit Tests

The purpose of a LTT testplan is to test DUT outputs (signals) against certain limits. Hence, the limit test is the most important TestStand concept for LTT.

TestStand offers 3 [standard limit test types](/ltt/documentation/ltt-gui-manual/teststand/limittests/standardlimittests.md):

* numeric limit test
* string limit test
* pass/fail test

The LTT software adds a fourth type of limit test - the [LTT limit test](/ltt/documentation/ltt-gui-manual/teststand/limittests/lttlimittests.md). The LTT limit test is a combination of the numeric and string limit tests and allows limits to be [configured by XML file](/ltt/documentation/ltt-gui-manual/configuration/generatedfiles/limitsconfiguration.md). That way it is easily possible to change limits without changing the the testplan itself. Additionally the LTT limit test step provides a **limit selection panel** in TestStand, where you can easily **select the signal and limit** you want to test.

![LTT Limit Test Dialog](/files/RaDq21FpUT4anPGw9gKF)


---

# 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.irs.systems/ltt/documentation/ltt-gui-manual/teststand/limittests.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.