> 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/testwheel/introduction.md).

# Introduction

#### Welcome to TestWheel

TestWheel is an AI-augmented test automation platform designed to help teams create, manage, execute, and maintain automated software tests with minimal coding.

The platform brings together web functional testing, API testing, performance testing, mobile testing, and desktop testing within a centralized environment.

TestWheel provides several approaches to test creation, including Excel-based test templates, Record and Playback, manual test case conversion, and AI-assisted automation. These options help teams reuse existing test assets, reduce repetitive testing effort, and simplify ongoing test maintenance.

Use this documentation as a guide to getting started with [TestWheel](https://app.testwheel.com/login), exploring its capabilities, and making the most of its features to streamline your testing processes.

<figure><img src="https://4225752331-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfpdbhL4mnjdXkFbYOzps%2Fuploads%2FpSBwlKfbdz0OzNr2b9Tx%2Fimage.png?alt=media&amp;token=775171bc-c1aa-4db2-9dab-c629666c046a" alt=""><figcaption></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/testwheel/introduction.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.
