Use shared assets

Shared assets are modules, reusable test steps, test data, test cases, parameter sets, mobile connections, API connections, DI connections, and capability sets that you create and maintain in a common asset library. They allow your team to reuse approved test assets across different workspaces and prevent duplicated effort.

• You can use them, but you can't edit them. For example, you can use shared test data in your test cases, but you can't use test data modules to create, edit, or delete shared test data.

• All assets you use from the Shared assets tab behave as shared assets, even if they come from your own workspace. We recommend using the User assets tab for your own assets instead.

• Sharing a test case includes its module and reusable test step dependencies but doesn't include test data or connection dependencies.

There are a few situations where shared assets can cause your test cases or playlists to fail:

• If a shared asset you use gets updated.

• If a shared asset you use gets deleted.

• If an administrator removes a workspace as a shared asset library.

Use shared assets

The Shared assets tab lets you reuse your team's shared modules, reusable test steps, and test data. You'll find this tab in a test case, in a reusable test step, and on the test data page. Parameter sets from shared workspaces appear in the Shared workspaces tab. Modules don't have a Shared assets tab because they can't reference other shared assets.

Depending on where you access this tab, you can do the following: 

• Jump to an asset in the shared library.

• Add a shared test case or reusable test step to whatever you're working on.

• Add a shared test case, reusable test step, parameter set, connection, or capability set to whatever you're working on.

• View references of a shared test case or reusable test step to see where it's used.

• View references of a shared test case, reusable test step, parameter set, connection, or capability set to see where it's used.

What's next

Now that you know how to use shared assets, why not put them to work? Next up: do a trial run. Trial runs help you find and fix issues, so you can make your tests as stable and reliable as possible.