Prerequisites
You have at least two Test Cases in the same project:
What are Reusable Tests?
Reusable Tests let you build a Test Case once, then reuse it inside other Test Cases as a single step.
Instead of copying and pasting steps between tests, you insert a Reusable Test Case step that references another Test Case. When the Main Test Case runs, Thunders executes the referenced Test Case’s steps as part of the same run.
Why Reusable Tests?
Reusable Tests speed up authoring and reduce maintenance:
Reduce duplication by centralizing common flows (login, onboarding, checkout setup, etc.).
Improve consistency because updates to the reusable flow apply everywhere it’s used.
This feature is ideal when your project has repeated setup actions, shared navigation, or repeated assertions.
How to Use Reusable Tests
1. Create the Reusable Test Case (your “module”)
Create a new Test Case that represents a reusable flow.
Recommendations:
Keep it focused on one goal (example: “Login”, “Create user”, “Go to Settings page”).
Use clear step names since this will appear in many places.
2. Open the Main Test Case
Open (or create) the Test Case where you want to reuse that flow.
3. Add the Reusable Test Case as a Step
In the Main Test Case steps:
Click Add step
Choose Existing Test Case
Select the Test Case you want to reuse
Once added, it should appear in the Main Test Case, representing the entire reusable flow.
4. Run the Main Test Case
When you run the Main Test Case:
The steps of the reused test will be executed as if they were part of the test case being executed.
After completing the reusable test steps, execution continues with the main test's remaining steps.
Editing Rules (What to Expect)
Reordering and removing Reusable Steps
In the Main Test Case, you can:
Reorder the reusable step among other steps.
Remove the reusable step from the Main Test Case.
Replace the reusable step by another step of any type.
Editing the reusable content
To change what the reusable flow does:
Edit the Reusable Test Case itself, not the Main Test Case.
This keeps a single source of truth for the reusable flow.
Troubleshooting / FAQ
Some test cases in the selection list are grayed out with a "would create circular reference" warning — why?
This is a protection we added to prevent circular references between reusable tests. If Test Case A reuses Test Case B, then Test Case B cannot reuse Test Case A (directly or indirectly through other test cases). The grayed-out test cases would create such a loop if selected.
What happens to my previous runs when I edit a reusable test case?
Old runs will keep the old version of the reused test. Only new runs will use the updated version of the reusable test case.
If I update the reusable test case, do all main tests update automatically?
Yes. Any Main Test Case referencing that reusable test will use the updated version the next time it runs.
What is the best practice for reusable tests?
Use them for shared flows that are stable and broadly used.
Keep them small and composable.
Name them clearly so they read well inside other test cases (example: “Reusable: Login (Standard User)”).
Are there any limitations on reusable tests?
Yes, there are today:
Copilot can remove or reorder reused tests, but it can't add new ones.
Test Cases containing discovery steps can't be reused.