> 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/how-it-works.md).

# How it works

TestWheel is an AI-augmented test automation platform designed to simplify the creation, execution, and maintenance of automated software tests. It provides a centralized environment for functional web testing, API testing, performance and load testing, mobile testing, desktop testing, and application security testing.

TestWheel follows a Plan, Build, and Run framework that helps users organize their testing activities, create reusable automated tests, execute them, and analyze the results.

#### 1. Plan Your Testing

The first step is to create an application in TestWheel and identify the testing scenarios you want to automate.

Users can organize their testing activities by application, select the appropriate testing type, and identify the workflows or functionality they want to validate.

Depending on the testing requirements, users can prepare the necessary test data, application details, authentication information, and execution environments.

#### 2. Build Your Tests

Once the testing scenarios have been identified, users can begin creating their automated tests.

TestWheel offers several methods for creating test cases, including:

**Excel-Based Test Creation:** Define test steps, UI elements, and test data using structured Excel templates.

**Record and Playback:** Record user interactions with a web application and convert them into reusable automated test steps.

**Manual Test Case Conversion:** Use AI-assisted conversion to transform existing manual test cases into automated tests.

**AI-Assisted Test Creation:** Generate test cases and automation workflows using supported AI features.

**Selenium Script Conversion:** Import and convert existing Selenium automation into TestWheel-compatible tests.

TestWheel uses a framework based on the Page Object Model, separating test data and UI elements from the underlying automation logic. This helps improve test reusability and simplifies maintenance when applications change.

Available test creation methods vary depending on the type of testing being performed.

#### 3. Run Your Tests

After creating and configuring test cases, users can execute their automated tests through the TestWheel platform.

Depending on the testing type, tests can be executed against supported browsers, applications, devices, and testing environments.

TestWheel also supports repeated execution of existing test cases, allowing teams to perform regression testing as applications are updated.

#### 4. Review Test Results

Once execution is complete, TestWheel provides reports that help users review test outcomes and identify potential issues.

Depending on the testing type, available reporting information may include:

* Pass and fail status for individual test steps and test cases
* Execution logs and error details
* Screenshots and video recordings
* Test execution statistics and summaries
* Performance metrics, charts, and APDEX reporting for load tests

These results help users identify failed test cases, investigate issues, and determine whether additional testing or corrections are needed.

#### 5. Maintain and Reuse Your Tests

TestWheel allows users to update and reuse existing test cases as applications and testing requirements change.

Users can modify test steps, update test data, and rerun automated tests without recreating the entire workflow.

For supported functional tests, TestWheel also provides AI-assisted self-healing capabilities to help identify and manage changes to application UI elements.

By maintaining reusable test cases and regularly reviewing execution results, teams can reduce repetitive testing effort and improve the efficiency of their testing process.


---

# 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/how-it-works.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.
