> 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.md).

# Data Parametrization

Data Parameterization allows you to run the same test steps with different sets of input values. You can provide input values directly hardcoded in the test steps or use an Excel sheet or Data Table when you need to execute the same test with multiple sets of data. This allows you to use one test case to test the same scenario with different input data, instead of creating separate test cases for each data set.

Avo Assure supports the following methods for Data Parameterization:

* **Excel sheet**: Use an excel sheet to store multiple sets of input values and use them during test execution.
* **Data Table**: Use a Data Table in Test Data Management to store and manage multiple sets of input values within Avo Assure.

Both methods allow you to run the same test steps with different data, making it easier to manage test data and reuse test cases.

This article explains how to configure data parameterization using an excel sheet or Data Table.

### Prerequisites

Ensure the following requirements are met before performing data parameterization in Avo Assure:

* Avo Assure Client is installed and connected to Avo Assure.
* The required test data is available in an Excel sheet or Data Table.
* The Excel file or Data Table is accessible from the configured location.
* The required test case flow is designed.


---

# 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-test-case-section/features-in-test-case-section-1/data-parametrization.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.