Skip to main content
Space Cadet
September 30, 2026
Question

How to manage duplicate Reusable Test Step Blocks (RTSB) when exporting test cases to Tosca Cloud?

  • September 30, 2026
  • 2 replies
  • 27 views

Hi everyone,

I’m currently migrating/exporting test cases from Tosca Commander into Tosca Cloud and running into an issue with duplicate assets.

Scenario:

When uploading test cases that share connected Reusable Test Step Blocks (RTSB) and Modules:

  • Test Case 1 is uploaded: its associated Modules and Reusable Test Steps are uploaded.

  • Test Case 2 is uploaded: duplicate/separate instances of the Modules and Reusable Test Steps are created in the cloud.

While Tosca Cloud provides a built-in Merge function for Modules to consolidate redundant UI elements, there doesn't seem to be a similar automated merge option for Reusable Test Step Blocks (Libraries).

Questions:

  1. What is the recommended workflow/best practice in Tosca Cloud to handle duplicate Reusable Test Step Blocks created during exports?

  2. Is manual refactoring (moving steps into a single primary RTSB and updating references across test cases) the only current solution, or is there a bulk-update/re-linking feature planned for cloud libraries?

Any tips or insights on how you manage RTSB deduplication in Tosca Cloud would be greatly appreciated!

Thanks!

2 replies

سامان ذوالفقاریان
Ensign
September 30, 2026

Hi Olivia,

This is a common behavior when migrating test assets incrementally from Tosca Commander to Tosca Cloud. When test cases are uploaded individually, Tosca Cloud processes each upload payload independently, resulting in duplicated Reusable Test Step Blocks (RTSBs) and Modules.

Here are the recommended best practices and current options to address this:

1. Best Practice: Batch Export from Tosca Commander

To prevent RTSB duplication during export:

Group and Export Together: Instead of uploading Test Case 1 and Test Case 2 separately, select both Test Cases along with their shared TestStepLibraries / RTSBs (or export the entire parent Component Folder) in a single export batch.

When uploaded as a unified package, Tosca Cloud recognizes shared dependencies and maintains a single reference for the RTSB instead of recreating it.

2. Pre-Migration Optimization

Before exporting from Commander:

Run a clean-up in Tosca Commander using Find Unused Elements to purge orphan RTSBs.

Ensure all shared steps strictly reference a single, centralized TestStepLibrary prior to initiating the cloud export.

3. Current Handling for Existing Duplicates

Modules vs. RTSBs: As you noted, Tosca Cloud offers built-in merging for UI Modules, but automated deduplication/auto-merging for RTSBs (Libraries) is currently not available post-upload.

Workaround: For assets already in the cloud, manual refactoring is required—re-linking the test steps in Test Case 2 to point to the primary RTSB created during Test Case 1's upload, and subsequently removing the duplicate RTSB asset.

Batching the assets at the Commander level before export remains the most effective solution to avoid manual re-linking in Tosca Cloud.

Hope this helps!

Space Cadet
September 30, 2026

Understood. Since the assets are already in Tosca Cloud, I’ll manually update Test Case 2 to point to the primary RTSB created in Test Case 1, then delete the duplicate RTSB to keep the workspace clean. Thank you!