Selecting automation

To pair automations with test cases, select an automation published to Orchestrator.

Note: If a Test Manager test case links to an automation from both Studio and Orchestrator, the automation selected from Orchestrator has priority over the automation linked from Studio.

前提条件

Note: If you select an automation directly in Test Manager, the selected automation is not considered if the Allow execution legacy context setting is enabled (for example, when no execution folder is selected at the project or test set level). Therefore, if you want to select automations directly in Test Manager, we recommend you to disable the Allow legacy execution context tenant setting.

To select an automation from Orchestrator, make sure to perform the following:

• Publish a Studio project to the Tenant Package Feed or to another Orchestrator folder feed.
• Have one of the following roles assigned to yourself:
  • Automation User
  • Any default role with administrative privileges
  Tip: Primarily, a user requires permissions to edit a test case in order to select an automation directly in Test Manager. Additional useful permissions in this context include having the Automation User role or any role with administrative privileges.

  For more information on default tenant roles visit Tenant default roles.

手順

To select an automation for a test case, follow these steps:

1. Go to the Test Case section of your project.
2. Open a test case.
3. Select the Automation tab.
4. Choose Select Automation.

   This action opens the Select Automation right-hand menu.

   1. From the Package Source dropdown list, select a feed from the corresponding Orchestrator instance.

      This feed should contain the Studio test case you intend to link to the Test Manager test case. The default selection is Tenant Package Feed.

      Only folders with their own feeds appear in the Package Source dropdown list. In a folder hierarchy scenario, only the parent folder displays in the dropdown list as all subfolders share the same feed.

      Note: The available package feed options are the ones for which you have administrative rights.
   2. After you choose the package feed, you can select an automation from that location.

      The automation name appears under Test Case Name, and the published package name under Package.

5. Select Save to confirm the changes.

   After you select the automation from an Orchestrator package feed, you can check automation details in these fields:

   • Package TestCase Name: The name of the Studio test case published to Orchestrator.
   • Package Name: The name of the package used to publish the chosen automation.
   • Package Source: The Orchestrator feed where you published the package.

Updating automation

To update the automation that you selected from an Orchestrator feed, follow these steps:

1. Go to the Test Case section of your project.
2. Open a test case.
3. Select the Automation tab.
4. Choose Update Automation.

   This action opens the Select Automation right-hand menu.

   1. From the Package Source dropdown list, select a feed from the corresponding Orchestrator instance.

      This feed is the one containing the Studio test case that you intend to link with the Test Manager test case.

      The default selection is Tenant Package Feed.

      Note: The available package feed options are the ones you have administrative rights over.
   2. After you choose the package feed, you can select an automation from that location.

      The automation name appears under Test Case Name, and the published package name under Package.

5. Select Save to confirm the changes.

次のステップ

To execute a test set that contains test cases with automations selected from Orchestrator, you can specify the particular package and version to run the test cases. This allows Test Manager to execute test cases linked to automations from several packages within your Orchestrator feeds, using only a selected package and version.

For more information on configuring a specific execution folder and selecting a package and version, visit Configuring test sets for specific execution folders.