When building web tests, it’s easy to repeat the same flows (logins, logouts, navigation, setup).With Reusable Components, you define these once and reuse them anywhere. Edit in one place, and the change automatically updates every test and monitor that uses it — keeping your suite modular, consistent, and easy to maintain.
Let’s walk through how it works 👇
1. Creating a reusable component
a. From an existing test
Start by opening any of your existing tests that contains a sequence you use frequently — for example, a Login flow.
Open the test in the editor.
Identify the step group you want to reuse (e.g. entering credentials and clicking "Sign in").
Click “Create reusable component”.
Give it a name (like Login flow) and add it to your library as a reusable component.
Once you’ve done this, your component becomes available in your product tests library — ready to be added to other tests.
--
b. From scratch
You can also create a reusable component without starting from an existing test.
Go to Tests → Reusable Components, then click “+ Create new reusable”.
From here, you can build a new component from the ground up, just like you would when designing a test.
This tab is also where you can:
Browse all your reusable components in one place.
See where each one is used across your tests.
Clean up unused components to keep your workspace organized.
💡 Tip
You can create components for anything repetitive — logins, navigations, setup flows, even cleanup steps.
2. Insert reusable component in your test
Now let’s use your freshly created component.
Create or open a new web test.
In the editor, click “Create new Group” or “Insert reusable component”.
Search for your reusable component (e.g. Login Component).
Insert it where you want in your test flow.
The imported block behaves just like normal steps — you can run, preview, and monitor your test as usual.
Behind the scenes, it’s linked to the original component definition, meaning it stays up to date automatically.
3. Update component and publish
Here’s the real magic: edit once, update everywhere.
Go back to your component and make any changes you need — for instance, update a locator, or add a new validation step.
When you’re done, click Publish.
All the tests (and monitors) using that component are automatically updated to the new version.
No more hunting down duplicated steps across dozens of tests — your change is applied globally and safely.
💡 Tip
Versioning ensures stability. Tests keep pointing to the previous version until you publish, so you can test your changes before rolling them out.
Reusable Components bring a more modular, maintainable approach to web testing.
They let you edit once and update everywhere, eliminate repetitive work, and keep your entire suite consistent.
Next time you find yourself re-creating the same steps, turn them into a reusable component — and watch how much smoother your workflow becomes.