Test Cases

Overview

In this topic, you can learn how to manage your test cases across all the projects and application versions. The test cases are part of test sets that are up for execution.

Conditions

• The test cases are created automatically when you publish a test package through Studio. For more information, see Application Testing.
• If an existing package is revised followed by an updated version being published, the test cases for the new version are automatically created. The new test cases show up alongside existing ones for the previous version. However, if the changes to the package only apply to the patch version, then the existing test cases are updated to reflect these changes, instead of creating new ones.
• When you publish a new test case version, the correspondent package is automatically updated to the latest version.
• If an existing project is cloned to represent a new application version (e.g. from v1.1.1 to v.1.2.0), you must manually publish this package and create a new process.
  Important:

  • For the robot to run test automation jobs in modern folders, make sure de default role Automation User exists and it is up to date.
  • You must first deploy a process from the published test case package before you can create and execute a test set.

Create Test Set

You can group together multiple test cases into a test set.

1. Log in to Orchestrator.
2. Open your folder.
3. Navigate to Testing > Test Cases.
4. Use the checkboxes to select individual test cases. Alternatively, you can choose Select all in the column header. You can modify the test case selection later in the test set configuration step.
5. Click Add test set.
6. Enter a Name and an optional Description for your test set and then click Create to continue.
   Note: For the Classic Folder, you need to select your Environment.
7. Configure the execution target:

   • For the Classic Folder, you can select the Robot from the dropdown menu.

   • For Modern Folders, you can select the user that is assigned to that specific folder. The default is set to Any User.

8. Select your Studio projects.
9. (Optional) You can edit the project version and toggle to Include Prerelease versions.
   
   

   

   
   
10. Define custom Arguments for your test cases to override default values at the test set level.

    Through the arguments, you can parameterize the test cases at runtime.

    Note: To define arguments, you need to have published a package with arguments.
11. Click Next to continue.
12. Modify test case selection if needed.
13. Click Save. Your test set is created and available on the Test Sets page.
    Tip:

    • Create test set on the Test Sets page
    • Execute individual test set
    • Add test schedule

Execute Test Case

You can execute individual test cases on the Test Cases page.

1. Log in to Orchestrator.
2. Open your folder.
3. Navigate to Testing > Test Cases.
4. Select a test case and click Execute.
5. Configure the execution target:
   • User: Select the user from the dropdown list that is assigned to that specific folder. The default is set to Any User.

   • Machine: Select the machine resource from the dropdown list.

     Note: For the Classic Folder, you need to select your Environment and then choose whether you want to allocate the execution dynamically or to specific robots.
6. Click Execute to confirm.

Delete Test Case

1. Open your folder in Orchestrator.
2. Navigate to Testing > Test Cases.
3. Select a test case and click Delete.
4. Click Ok to confirm.