> 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

This page describes about the Documents module in TestWheel Application

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="https://4225752331-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfpdbhL4mnjdXkFbYOzps%2Fuploads%2FM7TGfxkzg39ANBxRJhhF%2Fimage.png?alt=media&amp;token=7197ea1a-dd5e-4e13-90d6-fcaf23eec053" 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.testwheel.com/documents.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
