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

# Documents

After creating an application, the next step is to **import Test Data** for **Functional** and **Mobile Testing**. TestWheel offers multiple methods for importing test data, including:

* Uploading **Excel sheets**
* Using the **TestWheel Recorder** (Chrome Extension)
* Importing **Manual Test Cases** from **Azure DevOps**

In this section, we'll focus on uploading test data using **Excel sheets**.

Users should first download the predefined Excel templates available on the **Documents** page. After filling in the required information, the following three files must be uploaded to complete the test data setup:

* **Authentication.xlsx** – for login credentials and authentication data
* **UIProperties.xlsx** – for capturing UI elements and properties
* **UserData.xlsx** – for general test data and input values

Uploading these sheets ensures the application has all the necessary data to execute automated tests effectively.\ <br>

<figure><img src="/files/KS9KYslp3mLmf5yrIcle" alt=""><figcaption><p>Application Documets Page</p></figcaption></figure>


---

# 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.testwheel.com/documents.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.