Before Start Recording

Regardless of whether you use Ranorex Recorder within Ranorex Studio or as a stand-alone tool, not only the Recorder but also the system under test has to be prepared.

Prepare to Record

Before you start recording, you need to ensure that your system under test is ready to start with the manual test execution. In addition, consider the following points in order to avoid too much effort in cleaning up the recording and the repository afterwards.

  • Do not run multiple instances of your application under test if that is not part of the test case itself
  • By default, mouse movements are not recorded; for this reason please also perform mouse clicks in situations like when navigating through menus (or use Recorder Hotkeys to record mouse movements)
  • Think about which steps should be part of the final test
  • Try to keep recordings small in order to make them modular

Recorder Settings Dialog

Before running a new recording session, you can also configure Ranorex Recorder using the settings dialog. Click the 'Settings' button to open the settings dialog.
Settings for current recording file
Settings for current recording file
Default values used for every recording
Default values used for every recording

Current Recording

This tab primarily contains configuration parameters for code generation specific to the current recording. All settings on this tab page are stored within each recording.

Recording namespace:

Specifies the namespace used for the generated code.

Recording class name:

Specifies the class name used for the generated code.

Enable turbo mode for replay and generated code:

Is used to specify whether recorded delays between actions should be part of the generated code.

Generate replay reports:

This setting is used to turn the generation of reports during replay on or off.

Use item logging by default:

Activate this setting to turn on a default logging message for each action item.

Recorder Defaults

Within this tab you can specify global default values for every newly created recording. The settings are divided into three sections:

Recording

Record relative element coordinates: 

If checked, relative coordinates within a recognized element are recorded. Otherwise, actions will always be invoked on the "Center" of the recognized elements.

Capture a screenshot for each step:

Specifies whether a screenshot of the current action should be made during the recording.

Highlight clicked elements:

Specifies whether objects clicked during a recording should be highlighted.

Timings for new actions

Please note, that the following settings only affect newly created actions, not existing actions.

Key sequence split time (ms):

Use this setting to specify the maximum time for a key sequence during recording. If a key sequence exceeds the time set, it is split into several key sequences.

Mouse move time per action (ms):

Specifies the time in milliseconds used to move the mouse to the UI object related with the action.

Mouse related action time (ms):

Specifies the overall time in milliseconds used for a manually created mouse action. The value set for this setting is only taken into account for manually created actions or when the time of an action cannot be determined during recording.

Keyboard related action time (ms):

Specifies the default overall time in milliseconds used for a manually keyboard action. The value set for this setting is only taken into account for manually created actions or when the time of an action cannot be determined during recording.

Code Generation

Recording namespace:

Specifies the namespace used for the generated code.

Recording class name:

Specifies the class name used for the generated code.

Generate replay reports:

This setting is used to turn the generation of reports during replay on or off.

Use item logging by default:

Activate this setting to turn on a default logging message for each action item.