An action is an individual activity performed by a module. In Ranorex, there are two groups of actions: basic and smart actions. Basic actions represent direct user input, such as mouse clicks.
Smart actions represent more complex input or special functions, such as running a browser or carrying out a validation. Most actions are performed on repository items. Actions are managed in the actions table in the Recorder view.
Screencast: The screencast Introduction to actions walks you through information found in this chapter.
Basic actions
Basic actions represent direct user input with or on a device such as mouse clicks or keyboard input. These actions are automatically recorded when you perform them during a recording, but can also be added manually in the actions table. The table below lists the icon and name of each basic action. For more details about each basic action, refer to the following page: Action properties.
| Mouse | |
| Mouse wheel | |
| Touch | |
| Swipe gesture | |
| Key shortcut | |
| Key sequence | |
| Mobile key press |
Smart actions
Smart actions represent more complex UI interactions and functions. For example, the Run application action directly runs an executable from a specific path without the mouse clicks or keyboard interactions normally required. None of these actions are available during a recording except for the Validation action. For more details about each smart action, refer to Action properties.| Validation | |
| Invoke action | |
| Get value | |
| Set value | |
| Open browser | |
| Run application | |
| Run mobile application | |
| Deploy Android app | |
| Deploy iOS app | |
| Set device orientation | |
| Close application | |
| Wait for | |
| Log message | |
| Capture screenshot | |
| Create snapshot | |
| Separator | |
| Delay | |
| User code |
Actions in the actions table
Actions are managed in the actions table in the Recorder view.
Note: Actions are always listed chronologically, i.e. action #4 is executed before action #5.