> For the complete documentation index, see [llms.txt](https://funtest-1.gitbook.io/funtest-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://funtest-1.gitbook.io/funtest-documentation/creating-test-sequence/test-file-overview.md).
# Test File Overview
Test File in FunTEST is represented in LibreOffice Calc spreadsheet.
In the spreadsheet, all the necessary functionalities are defined including test sequence and test reporting.
Test File Example
### Each Test File has the following tabs
1. **Head**
This is where the general setting of the test file is defined such as test identification and variable list
Detailed view of HEAD tab
2. **TEST**
This is where your test sequence is defined with all necessary test steps
More detailed description of test file is in [TEST Sequence Tab](/funtest-documentation/creating-test-sequence/test-file-overview/test-sequence-tab.md)
3. **STAT**
This where you define any statics that will be saved from each test run
Detailed view of STAT tab
4. **VARIANT**\
This is where you can manage multiple variants of your product. Select the product variant you want to test and the test sequence will get automatically updated.
{% hint style="info" %}
Only Head and TEST tabs are mandatory. Other tabs are adding additional functionality that is often desired
{% endhint %}
---
# 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://funtest-1.gitbook.io/funtest-documentation/creating-test-sequence/test-file-overview.md?ask=&goal=
```
`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.