Test Management
Shared Steps
Shared steps are reusable test step sequences you can include in multiple test cases. Define a login flow, a setup routine, or a teardown sequence once — reuse it everywhere, and update it centrally when it needs to change.
Product news and testing tips.
Why it matters
The same login flow, copy-pasted everywhere
Login, logout, and setup sequences get typed into every test case that needs them — until there are 40 slightly-different copies.
One UI change, forty test cases to fix
Change a button label or a form field and every case that copy-pasted those steps now needs the same manual edit.
Drift between "identical" cases
Two cases that were copied from the same steps quietly diverge over months of small, uncoordinated edits.
How it works
Write the step sequence once, with placeholders for anything that varies per case — a username, an email, a product ID. Add the shared step to any test case that needs it; editing the shared step updates every case using it automatically.
- 1Navigate to /login
- 2Enter {username} in the email field
- 3Enter {password} in the password field
- 4Click “Sign in”
- 5Assert redirect to /dashboard
- Login with valid credentials redirects to dashboard
- Login preserves return URL after redirect
- Session persists across page reload
What you get
Define once
Write a step sequence — login, setup, teardown, navigation — a single time as a shared step.
Reuse everywhere
Add the same shared step to as many test cases as need it, instead of retyping the sequence.
Update centrally
Change the shared step once and it applies to every test case using it — no hunting down copies.
Parameterize with placeholders
Use placeholders like {email}, {username}, or {product_id} so the same shared step works with different data per case.
Ready to see it on your own test results?
Start free with Qualflare — connect your pipeline, upload a run, and see this in minutes.
Get Started FreeRelated features
Frequently asked questions
What are shared steps?
Shared steps are reusable test step sequences that can be included in multiple test cases — a login flow, a setup/teardown routine, a navigation path — written once and referenced everywhere it's needed, following the DRY principle.
Do shared steps support parameters?
Yes. A shared step can use placeholders like {email}, {username}, or {product_id}, so the same step definition works across cases that need different data.
What happens when I edit a shared step?
The change applies automatically to every test case that includes it — you edit the step once instead of hunting down and updating every copy.
Which plan includes Shared Steps?
Shared Steps is available on the Core plan and above.