Run & debug recordingsThe purpose of this chapter is to demonstrate how to run and debug existing recordings.
- Running a test, or a recording – in its simplest form – means replaying the recorded actions one after another and executing them step-by-step from the first to the last action.
- Putting it into a larger context, automated testing means replaying the test with a (large) number of different user data in an iterated way with different parameters and multiple test scenarios.
- This is where automated testing comes into play!
Turbo modeRanorex replays recordings just the way they have been recorded. This means that Ranorex simulates the time duration between actions in the way they were conducted by the user during recording. There are type dependent action time limits which define the maximum time between two different actions. But, the slower a test was recorded, the slower it will be re-played.
Turbo mode button in Ranorex Recorder
Good to know:
- When turned on, the replay is being performed nearly without time-delay between actions.
- The Turbo mode is applied to all actions of the recording module where it is activated
Run a recording moduleThis section shows you how to run a single recording module.
Running a recording module
Run test casesUsually, tests are not run based on recording modules, but as complete test cases from within the test suite view. The test suite is the central point of control for modularization and management of test cases. If you are not familiar with the test suite and its application, we recommend reading:
Switch to test suite view
Switching to test suite view
- The example test suite has the same name as the test project:
- The current test suite contains one test case default named
- Finally, the test case contains one recording module
- Checkboxes enable you to include/exclude test cases from test runs
Run the test case:
Running a test case
Success test report
- Finally, a test report indicating success, or failure is displayed as separate file view
Run shortcutsThe run of the test suite can always be started by means of shortcut symbols in the Studio toolbar.
Run & Stop shortcut buttons in Studio toolbar
Run optionsSometimes it is necessary not to run a complete recording, or test, but to control the run similar to debugging a computer program. These various run options are explained herein after.
Context menu on action item #4
- It is possible to run one or many (selected) action items isolated
- Only the selected action item(s) will be replayed
This option enables to run the complete recording from action #1 until the action prior to the selected action item.
This option enables to run the recording from a selected action item (including the item) until the end.
Finally, this option is a special type of ‘run option’ which usually is used to complete a yet uncompleted recording. By means of this option, you can run the test from the beginning to a defined ‘end’ and immediately continue the recording from there.
Debug – enable/disable on failWhenever an action leads to an exceptional state during the test the default reaction is that the test aborts. Sometimes this is not what you want the test run to do. So, there is the option to enable a continue on fail setting for an action.
Debug – inserting a log messageIf test cases become complex, or if tests are run with many user data and in numerous iterations with optional parameters, the tracking of progress by means of log messages in the report might be helpful.
Enabling/disabling debug modeRanorex allows enabling a debug mode which works in conjunction with installing breakpoints in the programming code. Therefore, this option is recommended for expert use only.
Ranorex Studio debug mode
Sample solutionIf you want to try the herein introduced options we invite you to download and use a prepared sample solution.
- Unzip the project directory to any folder on your computer
- Start Ranorex Studio and open the solution file