Give every test case a meaningful name
As your flows grow and branching expands coverage, clear naming becomes essential. The Name Test step allows you to assign a custom name to a test case as it moves through your flow.
Instead of seeing generic or automatically generated names in your run history, you can define descriptive, human-readable test names that explain exactly what path was taken.
This makes debugging faster, reporting clearer, and large packs easier to manage.
Why naming matters in branching flows
Branching allows one flow to generate many distinct test cases. Each branch can represent:
A different environment
A feature flag variation
A user state
A payment method
A configuration or locale
Without custom naming, these paths can be harder to interpret in results.
By placing a Name Test step after a branch, you make it obvious which route a specific test case followed.
For example:
Checkout – Guest
Checkout – Logged In
Checkout – With Discount Code
Checkout – Feature Flag Enabled
When reviewing results, the name instantly explains what was executed.
Names are cumulative
If you use multiple Name Test steps in a flow, the names are concatenated together to describe the final test case.
This is especially powerful in layered branching scenarios.
For example:
Branch by environment
Branch by feature flag
Branch by user state
Each Name Test node adds context, building a full description such as:
Staging – New Checkout – Logged In User
This gives you granular visibility without duplicating flows.
Make run history clearer and more useful
Clear naming improves:
Run history readability
Reporting clarity
Debugging speed
Stakeholder communication
When reviewing results, you immediately understand:
Which path was taken
What variation was tested
Why a failure occurred
Instead of deciphering flow structure, the information is already visible in the test name.
A best practice for structured flows
A simple, effective pattern is:
Branch
Immediately follow with Name Test
Continue building the scenario
This ensures every branch is documented and traceable in results.
As coverage grows, naming becomes just as important as the assertions themselves. The Name Test step keeps your automation organised, scalable, and easy to reason about, even as your flows become more sophisticated.