Variables

Learn how to use local and global variables in App Low Code Automation to reuse test data across multiple steps, making your tests flexible and easy to maintain.

Variables make your tests flexible, readable, and easy to maintain. There are two types of variables in App Low Code Automation:

• Local variables are used within a single test.
• Global variables can be used across any test in your project.

Use variables to eliminate hardcoded values, centralize data, and make your tests easier to update.

You can create a variable in the following ways:

• Set a static value in a test step. See Create a local variable.
• Extract text from an element on the app screen at run time. See Extract a value into a variable.
• Extract a value from an API response or a database query result. See Filter values extracted from API and database steps.
• Create a global variable on the App Low Code Automation dashboard. See Create a global variable.

Sample use case: Suppose you want to test login functionality across multiple test cases. Instead of hardcoding the password or email in every test step, you can create a variable called email and another called password. Reference these variables in your test steps, so you only need to update the value in one place if it changes. This makes your tests easier to maintain and reduces errors from inconsistent data.

Create a local variable

Local variables let you reuse values within the same test.

To create a local variable:

In the below example, the email address user@example.com is stored in the Email variable and the password 123abc is stored in the Password variable.

You can now reference this variable in other steps within the same test.

Extract a value into a variable

Some values change on every run, such as a one-time password, an order ID, or an order total. Hardcoding these values makes a test fail as soon as the value changes. Instead, extract the value at run time and store it in a variable that later steps can use. You can extract a value from an element on the app screen, from an API response, or from a database query result.

Extract text from an app element

Use the Set Variable name to text of AI prompt command to read the text of an element at run time.

To read more than one value, add a separate Set Variable name to text of AI prompt step for each value. A single step extracts one value from one element.

Filter the extracted text with a regular expression

A dynamic value is often embedded in a longer string, such as an order ID inside a confirmation sentence. Select Filter specific text and enter a regular expression to store only the matching part of the extracted text. The matched value appears under Value, below the Enter regex field, so you can confirm the pattern before you save the step.

The following table shows some common patterns:

For more details on regular expressions and advanced patterns, see the regular expressions guide and the regex cheat sheet.

Filter values extracted from API and database steps

• Call API: Narrows the value that the JSON path or the XPath returns. For more information, see Call an API and extract values.
• Run DB query: Narrows the value that the query returns. For more information, see Data-driven testing.

In both steps, the regular expression runs on the value that the step already extracts. It narrows the result instead of replacing the JSON path, the XPath, or the query.

Create a global variable

Global variables help you share data across multiple tests and modules.

To create a global variable:

Manage global variables

In the Global variables section, you see a list of all global variables. In the USED IN column, you can see how many tests use each global variable.

To delete a global variable, click the ︙ icon next to it, then click Delete. In the dialog, click Delete again to confirm.

Import variables into a test

You can import both local and global variables into your test steps:

Variables help you centralize and manage data, making your tests easier to update and maintain. For more details, refer to the documentation or reach out to support.