- 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)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Audit
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Other Configurations
- Integrations
- Classic Robots
- Host administration
- Organization administration
- Troubleshooting
Test Executions
In this topic, you can learn how to manage your test executions. The test executions serve as an immutable record of the execution of any respective test set, at a specific point in time. By comparison, the test set is always subject to change, as it can target a different application version or its test case selection can be modified.
You can re-execute test sets after a previous run. The new test case result will override the previous one shown on the Test Executions page.
Be aware that you cannot re-execute test cases from a Test Set with enabled coverage calculation.
You can view information on the activities that have been covered during a test execution. This option is also available in Studio, as Activity Coverage.
You can analyze test executions to understand what happened in instances where the execution failed or got stuck.
You can choose from the following actions to examine your test runs.
Actions |
Description |
Procedure |
---|---|---|
Execution details |
View Robot details, including execution attachments, data variation and screenshots. Make sure that you have Execution Media Permissions. |
|
View assertions |
View failed or passed assertions. |
|
View logs |
View and export a detailed log of execution events. |
|
To query for item related activities, you can use the Background Tasks, internally available through API. For more information on Orchestrator Permissions, see . For more information on test automation API, see Test Automation API Permissions.