Overview of the assertions, logs, affected requirements, and attachments collected in a test case execution log.

As part of test reporting, execution logs hold information such as execution details (for example, data variation and screenshots), failed and passed assertions, and a detailed log of execution events. Robot and Assertion logs are available in real-time as soon as the test case starts executing. You can also view the machine on which the test runs and the robot used to run the execution.

A test case log opens when you select a test case Key, or result, in a test execution.

Figure 1. Overview of the execution details of a test case log

The following sections describe the type of information that is collected during test case execution.

Failed or passed assertions, for example the Verify expression activity, and associated screenshots if any were taken during test case execution appear in the Assertions tab. For more information on making sure Orchestrator takes screenshots during executions, see the following resources:

The RobotLogs include INFO level logs, with information about processes, execution robot, and event logs, including failures.

The icon opens the Logs tab of the selected test case, with a detailed description of the failure.

The requirements that are assigned to the test case that has been executed appear in the Affected requirements tab. You can use this tab to go directly to the affected requirement.

You can view the following: