Best practices for configuring test sets

Recommendations for aligning package feeds, folder access, and robot assignments when configuring test sets across teams.

These practices describe how package feeds, folder access, and robot assignments affect the execution of test sets.

• A package published to two different Orchestrator folder feeds is treated as two distinct packages. If a test set's execution folder points to a feed other than the one a test case's automation is linked to, execution fails, even if a copy of the same package exists in that feed.
• Folder-level package feeds exist to enforce role-based access control (RBAC) and governance segregation between teams. Test Manager does not bypass this segregation to match packages across feeds.
• Running test cases whose automations are linked to different feeds in the same test set requires publishing the relevant packages to a shared feed, such as the tenant-level feed or a dedicated end-to-end (E2E) feed, and linking new test cases in Test Manager to the automations published there.
• Package feed access is scoped to the parent folder, not to subfolders. If departments share subfolders under the same parent folder, any department can see and execute packages published to that parent folder's feed, regardless of their own subfolder-level access. Full isolation between departments requires each one to have its own dedicated parent folder, with its own package feed, and its own Test Manager project.
• Only individually assigned users or robot accounts appear in the Select Robot dropdown. Members of a Directory Group granted folder access are not selectable as execution targets unless they are also assigned to the folder individually.