UI Recorder

Estimated reading: 4 minutes

The UI Recorder observes and captures user interactions within the application under test and automatically converts them into executable automation steps. Activities such as button clicks, text input, navigation, and other user interactions are recorded in sequence, enabling testers to rapidly create automated test workflows without manually defining each step. This approach accelerates test development, improves consistency, and reduces human error during workflow creation.

Enter the Testcase ID and Description. Configure the required settings under Configuration, and then click Launch Recorder to start the recording process.

Properties

INPUT

Testcase ID: Specifies a descriptive name for the test case. The name is displayed in generated reports. This property accepts a String value and can be provided either as a hardcoded value or through a String input.

Description: Specifies a summary of the test case, including the functionality being validated and the expected behavior. This property accepts a String value and can be provided either as a hardcoded value or through a String input.

Is Active: Enables or disables the UI Recorder activity for the selected test case. This property uses a Checkbox control and accepts a Boolean value. When selected (True), the activity is enabled and executed. When cleared (False), the activity is disabled and skipped during execution.

Is Configured: Enables or disables UI Recorder configuration for supported HTTP request methods. This property uses a Checkbox control and accepts a Boolean value. Supported methods include GET and POST. When selected (True), the configuration is enabled. When cleared (False), the configuration is disabled.

Report File Type: Specifies the format of the execution report. The supported report format is PDF.

Report File Path: Specifies the location where the execution report is saved. This property accepts a String value and can be provided either as a hardcoded value or through a String input.

MISC

Display Name: Specifies the name of the activity displayed within the workflow. This value can be customized to improve workflow readability and simplify identification of the activity.

Global SkipOnError: Specifies how the workflow handles errors encountered during the execution of this activity. This property accepts a Boolean value. When set to True, workflow execution continues even if the activity encounters an error. When set to False, workflow execution stops when an error occurs. If no value is provided, the property defaults to False.

Version: Displays the current version of the activity. This field is read-only and is automatically populated by the system.

OUTPUT

Execution Report: Contains detailed execution results for all recorded and executed steps. This output can be stored or returned as a String for validation, analysis, and reporting purposes.

Failed Report: Contains information about all steps that failed during execution. This output can be stored or referenced for troubleshooting and debugging and is returned as a String value.

Overall Status: Displays the final execution status of the test case. This output is returned as a String and can have a value of Passed or Failed. If one or more recorded steps fail during execution, the overall status is returned as Failed.

Result: Indicates whether the UI Recorder activity completed successfully. This output is returned as a Boolean value. A value of True indicates that the activity executed successfully without unexpected errors, while a value of False indicates that the activity failed due to an unexpected error.

XML File Path: Specifies the location where the XML execution report will be generated and saved. Providing a valid XML file path is mandatory to generate the report successfully. This property accepts a String value and can be provided either as a hardcoded value or through a String input. The report is generated in .xml format and stored at the specified location.
The report follows the naming convention ReportName_YYYYMMDD_HHMMSS.xml. For example, a generated report may be named UIRecorderReport_20260728_153045.xml.

Share this Doc

UI Recorder

Or copy link

CONTENTS
Robility Chatbot
Robility Assistant
Online