> 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/application/create-application.md). # Create Application From the Dashboard, users can access the **Application** module by clicking the **Application icon** available in the left-hand navigation panel. This page serves as the central workspace for managing all applications configured in TestWheel. Users can create new applications, manage existing configurations, enable testing features, and maintain version-specific testing assets from a single interface. The Applications page also provides quick access to application settings, execution options, and environment configurations required for **Functional** and **API testing** workflows.
To register a new application, users must click the **Add New Application** button, which opens the **Create Application** screen. In this section, users are required to provide application details such as the application name, description, application type, and environment configuration. Based on the testing requirement, users can select either **Web Application** or **REST API** as the application type. Additional capabilities such as **API Capture** can also be enabled during registration to monitor **API** requests during execution. After entering all required details, clicking the **Register** button saves the configuration and adds the application to the system
Once the application is successfully registered, **TestWheel** automatically redirects users to the **Applications** page, where the newly created application appears in the Application List table. For **Functional type** applications, a **Healing toggle** is displayed under the Healing column. Enabling this option activates the **Self-Healing** capability, which automatically identifies UI locator mismatches during test execution and updates the affected locators dynamically. This feature helps reduce automation failures caused by UI changes and minimizes the need for manual maintenance of test scripts.
When **API Capture** is enabled during application registration, the Applications page additionally displays two execution options: the **Browser** **Run icon** for executing **Web Functional tests** and the **API Run icon** for executing captured API test cases. To execute **Web Functional** testing, users must first upload the required testing documents in the **Documents module**. For **API testing**, users must configure and **fetch API** request data in the **API Test** page before execution.
The **Version Management** feature allows users to maintain separate testing assets for different releases of the same application. Using this functionality, teams can manage version-specific document uploads, configure release-wise test setups, isolate testing environments, and maintain historical version tracking for controlled regression testing. Organizing testing assets based on application versions helps improve release management, execution accuracy, and overall testing efficiency. For simplifying functional test creation, TestWheel provides the TestWheel Recorder, a browser-based recording utility available as a Chrome extension. Users can install the extension directly from the Chrome Web Store by clicking the [Click here](https://chromewebstore.google.com/detail/nhkpemikinijmhnogncmnnkdbolobhjk?utm_source=item-share-cb) **Install the TestWheel Recorder in user’s chrome browser from Chrome Web Store** link and launch it within the browser while accessing the target web application. Once the recorder is started, a separate recording tab opens where users can manually perform application actions. During recording, the plugin automatically captures user interactions, UI element properties, and browser actions in the background and displays the captured information in a structured format. After the recording process is completed, users can click the **Export to TestWheel** button to transfer the recorded test data directly into the corresponding application within TestWheel. The exported actions are automatically converted into reusable functional test assets, making them immediately available for Functional Testing execution and further test management activities.

TestWheel Recorder Screen


--- # 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/application/create-application.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.