As you have learned during the lessons before, the Recorder is typically used to record user actions. After recording a session it might be necessary to edit the recorded data for example to merge split key sequences or to delete single actions recorded by mistake. You can also add new actions like a new validation step which was not considered during a recording. In the following section you learn about:
The items listed within the 'Select Repository Item' dialog are the same as shown within the recording's repository. You can use the 'Search' text box to filter for elements. Read more about how to use repository search and how to add new UI elements here. Alternatively, you can also drag and drop repository items into the actions table of a recording as shown in the graphic on the right.
| Mouse | Adds a new mouse action item at the current position | |
| Mouse Wheel | Adds a new mouse wheel action item | |
Key Shortcut | Adds a new key shortcut action item (e.g. {F1}, {ENTER}) | |
| Key Sequence | Adds a new key sequence action item (e.g. "Hello") | |
| Validation | Adds a new validation action item | |
| Invoke Action | Adds a new invoke action item (e.g. call method 'Select' for a UI element of type list item) | |
| Set Value | Adds a new set value action to set an attribute value (e.g. 'Text' for a UI element of type text) | |
| Open Browser | Opens a browser and navigates to the given URL | |
| Run Application | Runs an application at the given directory and file path | |
| Close Application | Closes an application or web site containing the given repository item, respectively | |
Wait For Not Exists | Waits for disappearance of the given repository item Note: This action can be used for any type of UI element. | |
| Report | Adds a new report action item Note: Additionally to the standard report levels, you can define custom report levels by changing the level from "Info" to "Custom". | |
| Delay | Adds a new delay action item | |
| User Code | Adds a new user code action item which is used to implement a user specific validation in code for example |
Use the action item 'Validate' to check the attributes, images or different states of a repository item. Open the property grid to configure the behavior of a failed or successful validation individually.
| Action | Specifies the type of validation (e.g. Exists, NotExists, AttributeEqual, etc.) |
| Continue on Fail | Specifies whether to stop replaying in case of a failed validation or not |
| Create Screenshot | Specifies when to create a screenshot of the validated element (Never, OnFail, OnSucess or Always) |
Match Name | Specifies the name of the item's attribute to check |
| Match Value | Specifies the expected value used for validation |
Report Level On Failure | Specifies the report level in case of a failed validation Note: This setting has no effect on test case error behavior |
| Report Level On Success | Specifies the report level in case of a succeded validation |
By default each newly created recording refers to the main repository file. To create a new repository or to refer to another repository simply open the drop down menu from the repositories toolbar as shown below.

Online User Guide
download as: PDF (20.3MB)
Ranorex Tutorial
(PDF file, 13.5MB)