> 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/uploading-selenium-script.md).
# Uploading Selenium Script
The **Selenium Reverse Engineering** feature in TestWheel enables users to upload existing Selenium automation scripts and automatically convert them into a structured **Page Object Model (POM)** framework.
The **Selenium Script** module allows users to upload, manage, and execute Selenium automation scripts directly within the platform. This feature supports flexible automation integration by enabling teams to reuse existing Selenium test scripts instead of recreating automation frameworks manually, helping improve automation efficiency and centralized test management.
Supported upload formats include:
* **ZIP files** containing complete automation projects
* **Java files** containing individual Selenium test scripts
#### **Managing Uploaded Scripts**
After a successful upload, users can manage imported automation files directly within the platform. Uploaded files can be **rearranged** and organized in the required **execution sequence** to ensure proper automation flow.
* The **main execution** script should be placed **first**
* **Dependency** and **supporting files** should follow in the **correct order**
After the user clicks the **Submit** button in TestWheel, the uploaded document is saved successfully, and the system automatically navigates the user to the **Application** page.
---
# 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/uploading-selenium-script.md?ask=&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.
