Alias value
The Alias step lets you save a value or property as a new named value in the Value Store.
This is especially powerful when working with structured data such as API responses, CI/CD payloads, or nested objects. Instead of repeatedly referencing long object paths, you can extract exactly what you need and give it a clean, readable name.
Simplify complex object paths
When working with API responses or structured data, values often look like this:
body.user.name.first
That is accurate, but not always readable.
With an Alias step, you can map:
body.user.name.first → FirstName
From that point on, your test becomes easier to read and understand.
Instead of referencing a deep object path multiple times, you simply use FirstName.
Improve readability and maintainability
Alias values make your tests:
Easier to understand at a glance
Cleaner for reviewers and collaborators
More resilient to structural changes
If the shape of your API response changes, you only need to update the Alias step. The rest of your test can remain untouched.
This dramatically reduces maintenance effort, especially in larger test packs.
Ideal use cases
Alias is particularly useful when:
Extracting values from API GET, POST, or PUT responses
Working with nested JSON objects
Receiving structured data from CI/CD pipelines
Parsing complex objects stored in the Value Store
Preparing values for later assertions or form inputs
It allows you to create meaningful, domain-specific variable names that reflect the business logic of your test.
Make tests more expressive
Automation should be readable.
Aliasing turns raw technical object paths into business-relevant terms, making your flows clearer for automation engineers, developers, and stakeholders reviewing results.
Instead of exposing data structure complexity throughout your test, you isolate it in one place.
Cleaner names. Cleaner logic. Lower maintenance.