Shared / Reusable Test Steps
Starter+Steps Library lets you define a reusable sequence of test steps once and insert them into any number of test cases across your project. When a shared step is updated, all references are versioned so existing test cases remain stable.
Overview
Steps Library solves the problem of duplicated step sequences across your test suite. Common examples include:
- Login / Authentication flows that precede many tests
- Add-to-cart sequences reused across checkout tests
- Account setup or teardown steps
- Test data preparation steps shared by multiple scenarios
Plan Limits — Steps Library
Creating a Shared Step
Go to Project → Steps Library and click "+ New Shared Step" to open the library editor.
- 1
Open Steps Library
Navigate to Project → Steps Library. Click "+ New Shared Step" to open the creation modal.
- 2
Fill in the details
Enter a name (required), optional description, category, and tags. Tags support comma separation (e.g. "login, auth, smoke").
- 3
Add steps
Define the step sequence just like you would in a regular test case: each row has a step description and an expected result.
- 4
Save
Click "Save". A unique ID is assigned (e.g. SS-001) and the shared step is immediately available to insert into any test case in the project.
| Field | Required | Description |
|---|---|---|
| Custom ID | Auto | Auto-assigned (e.g. SS-001). Cannot be changed. |
| Name | Yes | A clear label for the step group. Shown in the reference block inside test cases. |
| Description | No | Notes about what this step group does or when to use it. |
| Category | No | Group related shared steps (e.g. "Auth", "Checkout"). Used for filtering in the library. |
| Tags | No | Comma-separated labels for additional categorization (e.g. smoke, login). |
| Steps | Yes | The actual step sequence. Each row has a step action and an expected result. |
Managing the Library
The Steps Library page lists all shared steps for the current project. You can search by name or ID, filter by category, and sort by usage count.
Editing a Shared Step
Click a shared step row to open the editor. Any changes you save increment the version number (e.g. v1 → v2). Existing test case references continue to record the version they were inserted at, so your test history is preserved.
Deleting a Shared Step
Deleting a shared step from the library automatically converts all references to inline steps within the test cases that used it. No test cases lose any step content — the steps become regular (non-shared) steps.
Exporting the Library
Use the "Export CSV" button in the library toolbar to download all shared steps and their step definitions as a spreadsheet.
Inserting into Test Cases
Once a shared step exists in the library, you can insert it at any position in a test case's step list.
- 1
Open a test case
Click any test case to open its detail view.
- 2
Click "Insert Shared Step"
In the Steps section, click the "Insert Shared Step" button below the step list.
- 3
Search and select
The library modal shows all shared steps in the project. Search by name, ID, or category. Click a row to preview its steps.
- 4
Confirm
Click "Insert". A reference block appears in the step list showing the shared step ID, name, and version it was inserted at.
The reference block in the test case shows the shared step's ID, name, and version at time of insertion. When executing the test, the steps are expanded inline so testers see the full step details.
Inline Conversion
You can promote regular inline steps directly into a new shared step without leaving the test case editor. This is useful when you realize an existing step sequence should be reused elsewhere.
- 1
Select steps to convert
In the test case detail view, select one or more consecutive regular steps using the step checkboxes.
- 2
Convert to Shared Step
Click the "Convert to Shared Step" option from the step action menu (⋯ icon).
- 3
Name the shared step
A dialog asks you to give the new shared step a name. The selected steps become the body of the new shared step.
- 4
Done
The original inline steps are replaced by a shared step reference. The new shared step is added to the library and can be reused in other test cases.
Used By Tracking
Every shared step in the library shows a usage count — the number of test cases that currently reference it. Click the count to open the "Used by" panel, which lists every test case that uses this shared step, along with its folder and ID.
This is especially useful before editing or deleting a shared step: you can review the impact on test cases first.
Before editing a high-usage shared step, check the "Used by" list and communicate the change to your team. Editing increments the version — references in existing test cases record the version they were inserted at, so run history is not affected, but reviewers may want to re-verify the new version.
Version Management
Every time a shared step is saved with changes, its version number increments automatically (v1 → v2 → v3…). References in test cases record the version at the time they were inserted.
| Scenario | Behavior |
|---|---|
| Shared step edited | Version increments. All future insertions use the new version. Existing references show the version they were inserted at. |
| Test case executed | The steps expanded during execution reflect the version stored in the reference at that time. |
| Shared step deleted | All references are converted to inline steps using the last saved version. No step content is lost. |
Next Steps
Steps Library pairs well with the Requirements Traceability Matrix for comprehensive coverage visibility.