> 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-test-case-section/features-in-test-case-section-1/data-parametrization/through-excel-sheet-1.md).
# Data Parametrizing through Excel Sheet
Avo Assure allows you to use an Excel sheet to store and manage test data. You can use an Excel sheet to run the same test steps with multiple sets of input values. This helps you manage test data separately and reuse the same test case with different data sets.
To use data parameterization through Excel sheet, perform the following actions:
1. On the **Home** page, under **Projects**, select the required project.
2. Select **Design Studio** > **Test Case**.
3. Select the Test case and Test Step Group where you want to use data parameterization.
4. Select **Add Step** (**+**) icon and then select **Add Step Manually** to add a new test step.
5. From the **Element** column, select **@Generic**.
6. From the **Action** column, select [**Get Param**](/avo-assure/actions/generic/loops-and-condition-operations-1/get-param.md).
7. In the **Input Value** column, enter the Excel file path and sheet name according to the action syntax.
{% hint style="info" %}
**Note**:
* The Excel file must be stored in the unrestricted folder.
* In the File Explorer, right-click on the Excel file select **Copy as Path** option to copy the excel path.
* When you use the **Get Param** action, you must add both [**Start Loop**](/avo-assure/actions/generic/loops-and-condition-operations-1/start-loop.md) and [**End Loop**](/avo-assure/actions/generic/loops-and-condition-operations-1/end-loop.md) as required steps.
{% endhint %}
8. Select **Add Step** (**+**) icon and then select **Add Step Manually** to add a new test step.
9. From the **Element** column, select **@Generic**.
10. From the **Action** column, select **Start Loop** to start the extraction from Excel sheet.
11. After the **Start Loop** action, enter the required variable names for the captured element in the **Input Value** column, with each variable added within the pipe operators (**|**). For example: |URL|.
{% hint style="info" %}
**Note:** The variable names should match the Excel column names.
{% endhint %}
12. Select **Add Step** (**+**) icon and then select **Add Step Manually** to add a new test step.
13. From the **Element** column, select **@Generic**.
14. From the **Action** column, select **End Loop** to stop the fetching from Excel sheet.
{% hint style="info" %}
**Note**:
* Add all required steps that use Excel data before the **End Loop** step.
* If you do not add **Start Loop** or **End Loop**, a [dangling node error ](/avo-assure/error-logs.md)occurs during test execution.
{% endhint %}
15. Select **Save** to save the changes.
{% hint style="info" %}
**Note**: You can also refer to the [Excel Actions](/avo-assure/actions/excel.md) page for different types of actions.
{% 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 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.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-test-case-section/features-in-test-case-section-1/data-parametrization/through-excel-sheet-1.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.
