Shared Steps
Build reusable step sequences for common flows
Shared steps let you define a sequence of actions and verifications once, then reuse it across structured test cases.
When to use shared steps
Reach for shared steps whenever the same flow shows up in many tests:
- Logging in or switching accounts
- Navigating to a common starting page
- Accepting cookies or dismissing onboarding UI
- Creating seed data that several scenarios need
When something changes later, say the login form gains a new field, you update the shared steps once instead of editing every test case that logs in.
Creating shared steps
- Open Shared Steps in the sidebar.
- Click New Shared Steps.
- Enter a name and an optional description.
- Add Action and Verify steps, written in the same plain language as test case steps.
- Save.
Shared steps support credentials and assets just like structured test steps — type @ in Action or Verify text to mention them. Shared steps do not include Login, Screenshot, or Wait step types; use those on the parent test case when you need them.
Referencing in test cases
In a structured test case editor:
- Add a step and choose Shared Steps, or switch an existing step to that type.
- Pick the shared steps group from the picker.
- Save the test case.
The shared steps run in place at that point in the sequence. The test case stores a reference rather than a copy, so any updates to the shared steps apply the next time those tests run.
Managing shared steps
The Shared Steps list is where you open and edit existing groups. Keep names specific (Login as standard user, Open billing settings) so authors can pick the right one without opening it.
One caution: if you change shared steps that are widely used, re-run a representative suite to confirm the dependent cases still pass.