Shared steps & datasets

Shared steps save you from retyping common steps. Datasets let one test case run with many sets of data.

Shared steps

Open Materials → Shared steps to create a step you use often, such as signing in. A shared step has a Name, an Action and an Expected result.

In the case editor, click Insert shared step to add one to a case.

Datasets

A dataset is a table of values, for example payment methods, promo codes or locales. Open Materials → Datasets, click New dataset, give it a name, then add columns and rows.

Column names can use letters, digits and _, and can't start with a digit.

Use values in a case

Write $column in a step, a Gherkin scenario or free text, and the agent receives the value of that column. Write $ for a literal dollar sign.

• The editor flags a name that is not a column of any dataset in the project.
• Preview as shows the case with the values of a given row.

Run once per row

In a test plan, each row has a Dataset setting. Leave it on None — runs once, or pick a dataset: the case then runs once per row of the dataset, on every browser profile ticked for it.

1 case × 2 browser profiles × 3 dataset rows = 6 executions

Deleting a dataset moves it to the Trash for 30 days. Meanwhile, plan rows bound to it run once, and $column references find nothing to substitute.

Values per environment

A value can differ per environment. Under Values for, choose Every environment or a specific one. A value typed for an environment applies there only (it shows as "Set for …"). Left empty, the row's value applies.

Secret columns

Mark a column as secret for credentials. The agent types the value into the page but never shows it, neither in its reasoning nor in the results. The AI model is given a placeholder such as {{password}} instead of the value.