Global shared steps are only available on paid subscriptions (startup/ business/ enterprise).

Shared steps let you define reusable step sequences that stay synchronized across every test case that uses them.

Overview

Most test suites contain steps that repeat across many cases, logging in, navigating to a settings page, resetting state between tests. Instead of duplicating these steps in every test case (and updating each copy when the workflow changes), create them once as a shared step. Every test case that references the shared step receives the same content, and edits to the shared step propagate automatically to all linked cases.

Shared steps exist at two levels:

Project-level — available only within a single project.
Global (workspace-level) — available across every project in your workspace.

Creating a shared step

Inside a project, go to the Shared Steps section inside a project to create shared steps. Provide a descriptive title and one or more steps using + Add Step, just like defining steps in a test case.

A shared step can be a single action or a sequence of multiple steps representing a complete workflow (e.g., "Log in with SSO" might include five granular steps).

Child steps

Steps can be nested, add child steps under any parent step to represent hierarchical workflows. There is no depth limit, so you can structure complex procedures as deeply as needed.

Organizing with folders

Keep shared steps manageable by grouping them into folders:

Create root-level folders with + New folder.
Create child folders via the (…) menu on any existing folder.
Clone an entire folder (including its steps) to another location. Cloned folders are prefixed with [Cloned].

Global shared steps

Global shared steps work identically to project-level steps, except they are accessible from every project in your workspace. Use them when the same procedure applies across multiple projects, for example, a login flow tested on web, iOS, and Android projects simultaneously.

Create global shared steps from Workspace → Shared Steps.

Constraints to know:

You cannot convert an inline test case step directly into a global shared step. You can convert a project-level shared step into a global one (this is irreversible).
Global shared steps display a globe icon so you can distinguish them from project-level steps when attaching to a test case.

Adding a shared step to a test case

When creating or editing a test case, select Add Shared Step.

You can choose from both project-level and global shared steps. A preview is available before you commit, so you can confirm the step content.

Editing shared steps

Open the shared step from the Shared Steps section and select Edit. Any changes you save propagate immediately to every test case that references the step. This is the core value of shared steps, update once, apply everywhere.

Viewing linked test cases

Each shared step shows how many test cases reference it:

Project-level steps — the "Attached to" column links directly to the repository filtered to show all cases using that step.
Global steps — since they can span projects, the usage view lists every repository and case count.

Converting inline steps to shared steps

While editing a test case, you can convert any regular step into a project-level shared step. The step is extracted into the Shared Steps section, and the test case now references it. Adjust the title or content in the Shared Steps section afterward.

Bulk actions

Select multiple shared steps to:

Move them to a different folder.
Convert project-level steps to global shared steps (irreversible, the steps become available workspace-wide).
Delete them. On deletion you choose: permanently remove the steps from all test cases, or convert them into local (inline) steps first.

For global shared steps, bulk actions support move and delete.

FAQ

If I delete a shared step, do the test cases break?
No. You choose whether to delete the steps from all linked cases or convert them to local steps. Either way, no test case is left in a broken state.

Can I duplicate a shared step?
Yes. Use the Clone action on any shared step (project or global). Edit the clone's title before saving.