> For the complete documentation index, see [llms.txt](https://docs.qatts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qatts.com/using-qatts/web-automation/performing-web-automation.md).

# Performing Web Automation

To Perform Web Automation, follow the Below steps:

**STEP 1:** Create a [Feature](https://docs.qatts.com/administration/feature) and add a name according to your requirement.\
\
**STEP 2:** Create a [Functionality](https://docs.qatts.com/automation/functionality) and add a name according to your requirement.  The Excel Files should be saved in the specific Location. For Example:

**Document** --> **Test Data** --> **Product** --> **Code Branch** --> **Client** --> **Excel File**

**Note:** If not saved at the specific location then the Excel File link will not be visible in the Functionality.\
\
**STEP 3:** Now Create a [New Group](https://docs.qatts.com/automation/objects/new-group) based upon the requirement. 

**STEP 4:** Create an [UI Element](https://docs.qatts.com/automation/objects/ui-element).

* Naming should be similar to the web element and in Lowercase. Finding of locators.

**STEP 5:** Creation of [Product Element](https://docs.qatts.com/automation/objects/product-element).

* **Note**: Product Element name should be unique.

**STEP 6:** Creating [Test Cases](https://docs.qatts.com/execution/test-case) in the excel sheet.\
\
**STEP 7:** Sync the newly added test cases by clicking on sync button in test cases module.

![](/files/-Mjd_OssxsDRw_80P2jj)

* **Blue:** Will erase all the Test data.
* **Red:** Will [sync](https://docs.qatts.com/execution/test-case/details-by-functionality/sync) newly added data in the excel sheet.

**STEP 8:** Once Test cases synced, create the [Test Suite](https://docs.qatts.com/execution/suite).\
\
**STEP 9:** Run the Test Suite or can also make a new test run and add the functionality and test suite later.\
\
**STEP 10:** Finally, the desired result will be reflecting on the 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.qatts.com/using-qatts/web-automation/performing-web-automation.md?ask=<question>&goal=<endgoal>
```

`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.