> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/items/test-cases-management/test-data-or-variables-manager.md).

# Test data or Variables manager

Easily manage and reuse test data sets with the Variable Manager - parameterize test cases, update variables, and streamline data-driven testing in just a few clicks.

A test case can be parameterized with test data. Open a Test-case and open the Variable Manager by clicking on the Data tab in the left navigation bar. The screenshot below shows two data sets (Rick and Morty) for testing a login.&#x20;

The data is specified similarly to Excel. The Set Name represents the name of the test value set, and the columns represent the test variables (`Name, Last Name, Username, Password,` and `LoginResult)`. &#x20;

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2FqxVwBluRIg4NKdt20bj3%2Fimage.png?alt=media&amp;token=459429d2-a36e-4aec-bd4b-1db4a3bb9722" alt=""><figcaption><p>Variables manager view</p></figcaption></figure>

Open the Step designer in order to parameterize the test steps. Insert the variable Username by clicking on Insert Variable and then clicking on Username. A placeholder $Username is inserted. &#x20;

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2FBqD3KFH1ilJ6cOPwyqIG%2Fimage.png?alt=media&amp;token=be9d746b-3b93-4f02-9d92-c3dcf76315e4" alt=""><figcaption><p>Parameterizing the test steps</p></figcaption></figure>

If you [run ](/documentation/items/test-cases-management/manual-testing.md)the test case, you can choose the value set via a drop-down menu. &#x20;

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2FfUk2uunuv3zQqrFpvg4u%2Fimage.png?alt=media&amp;token=f076c284-7434-49b6-893d-372424db0b2c" alt=""><figcaption></figcaption></figure>

As you can see in the following screenshot, the placeholder is replaced with the given value. &#x20;

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2FuvdGixjGOlBDUxJkvMye%2Fimage.png?alt=media&amp;token=5ef94e14-8354-4f58-a1ea-3b9aad835108" alt=""><figcaption><p>Placeholder replaced with the value</p></figcaption></figure>

As soon as you make changes to the variable names, you will be asked whether the variables should be updated in the test steps in which they are used. If you confirm with Ok, the variable names are updated in the steps. If you click Cancel, the variable names in the steps are not replaced and will not be printed in future test executions. &#x20;

<figure><img src="http://aquawiki.andagon.com/pictures/drex_defining_data___using_variable_manager_for_parametrization_custom_5.png" alt=""><figcaption></figcaption></figure>

If two or more test cases should share their test data, you can synchronise it. To do so, open the test case that should use the data from another test case and go to 'Data'. Click on ![](http://aquawiki.andagon.com/pictures/drex_defining_data___using_variable_manager_for_parametrization_custom_6.png).&#x20;

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2FkWk97fBX0WcFQvwmqwJG%2Fimage.png?alt=media&amp;token=6ef16d0a-a720-46cd-827c-1faba32e20fb" alt=""><figcaption><p>Synchronizing the Test Case data</p></figcaption></figure>

Select the test case, whose data you want to use, and klick on 'Reuse data from selection'.&#x20;

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2F6o6oJZgkRf1WDPIle33L%2Fimage.png?alt=media&amp;token=00247d1a-c324-4e41-8b8e-8d8d1f26782b" alt=""><figcaption><p>Reusing data from other Test Case</p></figcaption></figure>

Now you can use the data from the other Test Case in this Test Case. If you want to keep the variables locally in this Test-case, click 'Copy over'.&#x20;

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2F2fgKit4mnWbxah3hw8gE%2Fimage.png?alt=media&amp;token=e04af3a3-f29c-488a-a8d6-cc4f28669e1e" alt=""><figcaption></figcaption></figure>

If you want to execute all or a selection of parameterized tests as a group of tests, you can have a look at [Test scenarios](/documentation/items/test-scenarios-management.md).


---

# 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.aqua-cloud.io/documentation/items/test-cases-management/test-data-or-variables-manager.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.
