Shared steps allows you to create a single step that can be shared across multiple test cases. This eliminates the need to recreate the same step manually for each test case and ensures consistency across all test cases in which the shared step is used.
Imagine that you have two different cases for a test suite - both require authorization into the internal system to proceed, so it will be one of the steps to recreate.
You could manually add an “Authorization” step to each test case individually, but it’s better to create a single shared step that you can consistently use across multiple test cases.
Shared steps are available both at a project level, and also at a workspace level.
Global Shared Steps (workspace-level)
Global shared steps work much like regular shared steps, but they are available across every project in your workspace instead of being limited to just one.
For instance, you might be testing the same product on web, iOS, and Android. All these test cases may require the same action such as logging into the application.
Instead of creating the same shared step in each project, you can create one global shared step and use it wherever it is needed.
You can create a global (workspace-level) Shared step, from workpsace >> shared steps.
Please note that steps that already exist in test cases or shared steps within a project cannot be converted into global shared steps.
Create a Shared step
Go to the Shared Steps section inside a project and create a new shared step
Provide a title for your shared step to identify it easily.
A shared step can either be a single step or a group of multiple steps.
Use the +Add Step button (located below the title field) to add individual steps, just like when creating steps for a test case.
It is currently not possible create nested steps inside of a shared step.
Bulk Actions
You can take two bulk actions for shared steps within the project:
1. Convert the selected shared steps into global shared steps. Please note that this action is irreversible. Use caution, as project-level shared steps will be converted to workspace-level shared steps, making them accessible to all team members.
2. Delete select shared steps. You can choose between permanently deleting all the steps where the shared steps are used, in test cases. Or, convert those steps into local regular steps before deletion.
For Global shared steps, you can select multiple test cases to delete at once. You'll have the same two options as project level shared steps, when deleting.
Convert a existing local step into Shared step:
While editing a test case, you can convert a regular step into a shared step. Adjust the newly created shared step later in the Shared Steps section.
Add Shared step to a test case:
When you create or edit a test case, select the Add Shared Step button to include either a project-level shared step or a global shared step.
You can preview a step before adding it to the test case.
Global shared steps have a 🌐 icon at the beginning so you can tell them apart.
Editing Shared steps:
You can update the shared step or global shared steps by selecting the Edit button in the Shared Steps section.
Any changes you make and save will automatically apply to every test case that uses that shared step, which helps keep everything consistent and up to date.
View linked test cases.
For both shared steps, within project and global – you can view the test cases the step is used in by.
For shared steps within a project, clicking the links in the ‘Attached to’ column will open the repository and show all the test cases where that step is used.
For Global shared steps, since they can be linked to multiple projects, you can view all repositories that use the step.
Cloning Shared steps:
You can easily create a copy of the shared steps (both project level and global) by cloning the step. You can edit the new step's title before cloning.
