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.
- Log in to Orchestrator.
- Open your folder.
- Navigate to Testing > Test Executions.
- Select a test run and go to More actions > Details.
- Select a test case and go to More actions > Re-execute.
- 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.
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.
- (Optional) Define custom Arguments for your test cases to override default values at the test set level. To define arguments, you need to have published a package with arguments.
- Click Execute to confirm.
You can analyze test executions to understand what happened in instances where the execution failed or got stuck.
You can view screenshots of failed test executions by navigating to Automations > Job > Job Details. To benefit from this feature, you need to enable execution media at the application level. For more information, see Execution Media Permissions.
You can choose from the following actions to examine your test runs.
View Robot details, including execution attachments, data variation and screenshots.
View failed or passed assertions.
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 About Roles. For more information on test automation API, see Test Automation API Permissions.
Updated 2 months ago