Recommended approaches for handling large datasets, Data Fabric-linked test data, and interdependent test cases.

Follow these recommendations for working with test case arguments and data in Test Manager.

If input values are extensive or need to vary across test runs, use data-driven testing instead of manually maintained parameters. Test Manager supports data-driven testing using Excel files. UiPath Data Service or Test Data Queues (managed through Orchestrator) can also be used for structured data and dependencies.

When a Data Fabric/Data Service entity is linked as test data, each row becomes its own test variation. Test Manager does not support grouping multiple rows into a single logical variation. If one variation needs multiple related records (for example, a transaction with multiple line items), a parent record serves as the variation driver, and activities in the workflow query the related child records from Data Fabric at runtime (for example, by a shared ID).

Multiple test cases can link to the same Data Fabric/Data Service entity when their data schemas match. The number of entities you need depends on the number of distinct data schemas across your test cases, not on the number of test cases. Before you create entities, review the data schemas of your data-driven test cases and reuse one entity for test cases that share a schema.

For test cases where one test case's output feeds another's input, use an external data store rather than relying on in-memory dependencies between test cases, for example:

If reuse in memory is critical, combine the relevant logic into a single workflow or test case instead.