- Getting started
- Project management
- Working with Change Impact Analysis
- Create test cases
- Assigning test cases to requirements
- Cloning test cases
- Exporting test cases
- Linking test cases in Studio to Test Manager
- Delete test cases
- Enabling governance at project level
- Disabling governance at project level
- Enabling governance at test-case level
- Disabling governance at test-case level
- Enabling or disabling governance in bulk for test cases
- Enforcing signing order for governed test cases
- Managing approvers for governed test cases
- Managing governed test cases in the In Work state
- Managing governed test cases in the In Review state
- Managing governed objects in the Signed state
- Managing comments for governed test cases
- Viewing governance information for test case logs
- Managing approvers for governed test case logs
- Managing governed test case logs in the In Work state
- Managing governed test case logs in the In Review state
- Managing governed test case logs in the Signed state
- Managing comments for governed test case logs
- Enabling governance at test case log level
- Disabling governance at test case log level
- Viewing and searching test cases
- Project operations and utilities
- Test Manager settings
- Tenant level settings
- General project settings
- Events
- Subscribing to events
- Subscribing to all events
- Unsubscribing from events
- Unsubscribing from all events
- Unsubscribing from the Notifications settings page
- Viewing notifications
- Filtering notifications
- Viewing email notifications
- Enabling email notifications for SMTP servers
- Viewing only unread notifications
- Marking all notifications as read
- Clearing all notifications
- Deleting notifications
- Customer managed keys encryption
- Audit logs
- ALM tool integration
- ALM tool integration
- Test Manager Connect
- Test Manager - Integration Service connector
- Outbound IP ranges for connectors
- Working with SAP Cloud ALM and Test Manager
- Step 1: Integrating SAP Cloud ALM with Test Manager
- Step 2: Creating automated test cases in SAP Cloud ALM
- Step 3: Creating automated test cases in Test Manager
- Step 4: Synchronizing test cases from Test Manager to SAP Cloud ALM
- Step 5: Assigning test automations to test cases
- Step 6: Executing test cases
- SAP test automation best practices
- Troubleshooting the Jira integration
- API integration
- Coding Agents for Testing
- Troubleshooting
Executing tests
Test execution options in Test Manager: manual executions invoked through the UI, automated executions run via Orchestrator, and autonomous executions run by Autopilot.
You can execute tests manually or automated. Manual test executions are invoked through Test Manager, whereas automated executions are invoked through Test Manager and executed via Orchestrator. Additionally, within one test set execution, each individual test case can be executed either manually or automated. This changes the execution type to Mixed.
You can execute test cases from a test set or, in Test Cloud, directly without a test set. To execute test cases from a test set individually, instead of all at once, create a pending execution. From any execution, you can choose to execute individual test cases either automated or manually.
The test execution and test case logs created by an execution carry the labels of the test set and test cases you ran. Use them to search and filter in the Results tab in Execution. For more information, refer to Test results.
Conditions
- You can use both Execute Manually and Execute Automated for test sets created in Test Manager as well as the linked test sets from Orchestrator.
- Only the test case versions included in the test set are executed. If you want to execute new test cases, you need to assign new versions to your test set. For Orchestrator test sets, you need to make sure that the latest packages are published.
- If Enforce Execution Order is enabled, you cannot select individual test cases to run or re-run from a test set. To re-run only specific test cases, such as failed ones, turn off Enforce Execution Order first. For more information, refer to Re-running only failed test cases.
- A test set can be executed via Serverless cloud robots if there is a cross-platform automation project published to Orchestrator and added to your folders. For more information, refer to Executing unattended automations with Serverless robots.
- Browser UI tests can run on Linux robots if the automation is a cross-platform project, and they are triggered from Test Manager like any other run. A Linux robot is an unattended robot that runs in a Docker container with its own Chrome or Chromium, so tests do not run in a user's own desktop session. UI automation on Linux is limited to Chrome and a subset of UI Automation activities, and Linux desktop applications are not supported. For more information, refer to Linux robots.
Automated execution
Automated execution refers to tests sets created in Test Manager which have an automation selected.
Automated test execution is unattended, so processes of type Testing do not appear in UiPath Assistant. Automated tests are triggered from Test Manager and run on a Testing (unattended) robot, or you can run a test from Studio and publish the results to Test Manager. Automations that generate test data are process automation and belong in regular Process projects.
Manual execution
Manual execution refers to test sets created in Test Manager, including test cases that have manual steps. Manual execution can be done for test sets created in Test Manager.
Autonomous execution
Autonomous execution refers to manual test cases that Autopilot runs automatically, without a scripted automation. Autonomous runs start from the Run autonomously option on the Manual Steps tab of a manual test case.
Autonomous execution is available only in Test Manager delivered via Test Cloud. For more information, refer to Autonomous Test Execution for Test Cloud and Running Autonomous Test Execution.