orchestrator
2023.10
false
- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Configuring automation capabilities
- Audit
- Settings - Tenant Level
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Other Configurations
- Integrations
- Host administration
- Organization administration
- Troubleshooting
Test Cases
Orchestrator User Guide
Last updated Nov 7, 2024
Test Cases
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. For more information, see Test Sets.
- 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
tov.1.2.0
), you must manually publish this package and create a new process.Important:- For the robot to run test automation jobs, 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.