# Test Configuration

{% hint style="info" %}
[Click](https://github.com/irs-systems/IRS-LTT/blob/GitBook/doc/30%20User%20Documentation/.gitbook/assets/ltt_test_config.xml) to open the test configuration file **ltt\_test\_config.xml**.
{% endhint %}

The test configuration file is an automatically generated file and contains all settings made in the [F10 - test parameter configuration](/ltt/documentation/ltt-gui-manual/lttgui/dialogs/f10testparameterconfiguration.md) and [F11 - test configuration](/ltt/documentation/ltt-gui-manual/lttgui/dialogs/f11testconfiguration.md) dialogs. It also contains some settings from the [F3 - project wizard](/ltt/documentation/ltt-gui-manual/lttgui/dialogs/f3projectwizard.md).

{% hint style="info" %}
All test configuration settings are stored in configuration database, but are also exported to XML. The Action Logs mechanism use this file as a form of **documentation** of the parameter changes over time.
{% endhint %}

The LTT TestStand process model also uses some of those informations for its own purpose.

As a summary, you will find in the test configuration file the following informations:

* what DUT types are available?
* what test groups are available?
* how many test stations are present and what test orders / DUT's are configured for them?
* what operation modes are available and what parameters do they have (per test group)?
* what operation mode <> TCC mappings are configured?
* what power supplies / temperature sensors are assigned to what test group?

{% hint style="warning" %}
Do not make any changes in this file as they will be overwritten by the GUI.
{% endhint %}


---

# 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://docs.irs.systems/ltt/documentation/ltt-gui-manual/configuration/generatedfiles/testconfiguration.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.