Organize & reuse

Reusable steps

Record a login once, give it Inputs, and use it in every test. Change it in one place and every test follows.

Steps that repeat in many tests — signing in, adding a product to the cart — are recorded once as Reusable steps. In a test they appear as a single step, e.g. Log in (email, password); change them and every test that uses them changes too. They can hold any kind of step: clicks, checks, waits, API requests, other tabs, even other Reusable steps.

They replace Flows

Flows from earlier versions are converted to Reusable steps automatically the first time a project opens (the old files stay on disk).

Create Reusable steps

Make reusable — select consecutive cards in the Action History and click Make reusable. Give it a name and a description; the values you typed are proposed as Inputs (passwords without a default). The cards are replaced by one call with the original values, so the test behaves the same; one Ctrl+Z undoes it.
＋ in the Reusable steps section of the Project tab — creates an empty one to record.
Suggestions — when three or more steps in a row are also in another saved test, a banner offers Make reusable; when they match existing Reusable steps, it offers to use them (Use “Log in”).

Inputs

Inputs are the values that change each time: an email, a product name. Inside the Reusable steps they are written {{input:email}} (the { } menu offers them only there). Each Input can have a default value, used when a test doesn’t set it. Renaming an Input rewrites it in every step; removing it puts its default back in place.

Variables saved inside Reusable steps stay inside, and a test’s data columns are not visible there: pass them as Inputs.

Edit and use them

Open (click the row in the Project tab) opens them in the recorder, marked by a purple chip next to the name: record and edit cards as in a test, set the Inputs, then Save.
To use them in a test, hover the gap between two cards and click + → Insert reusable, or Add to test from their menu.
The call card shows a field per Input, the steps inside (read-only), Open and Unpack, which turns the call back into normal steps with the values filled in.
Used in N lists the tests that call them; click one to open it on that step.

Renaming updates the tests

Renaming Reusable steps, or changing their Inputs or defaults, changes what the calling tests contain. Before saving, the app lists those tests: Save and update N saves and updates them all, Cancel saves nothing. Changing only the steps inside needs no update.

For Playwright users

TypeScript

// reusable/logIn.ts
export async function logIn(qa: { page: Page; context: BrowserContext; request: APIRequestContext }, inputs: { email: string; password: string }): Promise<void> {
  const { page } = qa;
  await page.getByLabel("Email").fill(inputs.email);
  // …
}

// in the test
await test.step("Log in", async () => {
  await logIn({ page, context, request }, { email: "demo@shop.test", password: qaSecret("password") });
});

Files live in the project’s reusable folder (<fn>.reusable.json + <fn>.ts) and are included in the export. The functions are regenerated at every Save and before every run.

Something unclear or missing? Write to info@actify-studio.com.

Create Reusable steps#

Inputs#

Edit and use them#

Renaming updates the tests#

Create Reusable steps

Inputs

Edit and use them

Renaming updates the tests