> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-element-repository-section/create-element-repository/capturing-web-elements.md).

# Creating Web Element Repository

Web element capture identifies the User Interface (UI) components from the Application Under Test (AUT) and adds them to a web element repository. The captured elements help you interact with UI components during test creation and execution. This article describes how to capture the web elements using Avo Assure.

## Prerequisite

Ensure that the Avo Assure Client is connected.

## Capturing Web UI Elements

To capture web elements, perform the following actions:

1. On the **Home** page, under **Projects**, select the required Project.
2. ​Select **Design Studio**.
3. ​On the **Element Repository** page, select the **Create Folder (+)** icon.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FKOPkNA1tZ9OGn2ttslBF%2Fimage.png?alt=media&amp;token=b31ce0bd-326e-41ca-ad77-2902a6a40575" alt=""><figcaption></figcaption></figure>

4. Select **Create main folder** to create a new element repository folder. A new folder appears.
5. In the **New Folder** text box, enter the element repository folder name.
6. In the newly created folder, select the Ellipsis (**...**) icon next to the repository name, and then select **Create Repository** > **Web** to create the element repository.
7. Select **Capture Elements**. The **Select Browser** dialog box opens.
8. Select the required browser, and then select **Capture**. The **Avo Assure Client – Capture** window opens.
9. In **Step 1: Enter URL** box, enter the URL of the AUT.

<img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F7rlbbGy4L0eHshSyRwkq%2Funknown.png?alt=media&amp;token=af42c290-370b-49c6-9468-b4d59c7df806" alt="" width="563">

10. Select **Navigate**. You are redirected to the specified URL.
11. In **Step 2: Capture Element**, select one of the following capture methods:
    * **Visible**: Captures visible elements in the AUT.
    * **All**: Captures all elements in the AUT for every Capture Type, including hidden elements.
    * **Manual**: Allows you to manually navigate to AUT and capture elements.
12. Depending on the selected capture method, perform one of the following actions:
    * **Visible** or **All**: From the **Capture Type** dropdown, select the element types to capture.
    * **Manual**: From the **Delay** dropdown, select a delay duration to capture the elements with longer loading time.
13. Select **Capture** to start the element capturing process.

{% hint style="info" %}
**Note:** You do not need to follow different steps to capture iFrame elements. Follow the same steps used for capturing other elements.
{% endhint %}

10. Select **Add**. The selected elements are added to the element repository.

{% hint style="info" %}
**Note**:

* Select **Locate** to highlight the corresponding elements in the application UI.
* Select **Delete** to remove the selected elements from the capture list.
  {% endhint %}


---

# 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.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-element-repository-section/create-element-repository/capturing-web-elements.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.
