This page is maintained for older versions of Rapise only. The latest documentation can be found at:
Settings View

Settings View

Top  Previous  Next


settings dialog



Use the Settings Dialog to change test specific settings.


How to Open

The Settings dialog is part of the Default Layout.



settings dialog, advanced

·CommandLine is a freeform text box.  Use it to specify values for global variables (beginning in g_) to pass the recorder and player.  You can view which global variables are available in the source files (such as Player.js, SeSCommon.js, etc).



settings dialog, execution

·CacheObjects: Remember object locations and try to reuse them for speed.  This is helpful with dialog based applications.
·CommandInterval: Time interval (in milliseconds) between script commands during script execution.
·IterationsCount: Your test script will be executed this many times consecutively during Playback.
·ObjectLookupAttemptInterval: This is the time Rapise will wait between attempts to locate an object.
·ObjectLookupAttempts: This is the number of times Rapise will attempt to locate an object.



settings dialog, recording

·BeautifySavedObjects affects how the Script Recorder writes object information to your test script.  If False, the object definition will be written as a single line:


var saved_script_objects={

   Balance:{"version":0,"object_type":"SeSSimulated","object_name":"Transaction Completed Successfully\n\nAccount 00000005  Balance:1046.00","object_class":"Static","object_role":"ROLE_SYSTEM_STATICTEXT","object_text":"Transaction Completed Successfully\n\nAccount 00000005  Balance:1046.00","locations":[{"locator_name":"Location","location":{"location":"4.4.4","window_name":"SmarteATM","window_class":"#32770"}},{"locator_name":"LocationPath","location":{"window_name":"SmarteATM","window_class":"#32770","path":[{"object_name":"Transaction Completed Successfully\n\nAccount 00000005  Balance:1046.00","object_class":"Static","object_role":"ROLE_SYSTEM_STATICTEXT"},{"object_name":"Transaction Completed Successfully\n\nAccount 00000005  Balance:1046.00","object_class":"Static","object_role":"ROLE_SYSTEM_WINDOW"},{"object_name":"SmarteATM","object_class":"#32770","object_role":"ROLE_SYSTEM_DIALOG"}]}}]}



If True, the object definition will be written in a manner that takes more space, but is easier to read and change:


var saved_script_objects={


   "version": 0,

   "object_type": "SeSSimulated",

   "object_name": "Transaction Completed Successfully\n\nAccount 

       00000005  Balance:1046.00",

   "object_class": "Static",

   "object_role": "ROLE_SYSTEM_STATICTEXT",

   "object_text": "Transaction Completed Successfully\n\nAccount

        00000005  Balance:1046.00",

   "locations": [


         "locator_name": "Location",

         "location": {

            "location": "4.4.4",

            "window_name": "SmarteATM",

            "window_class": "#32770"




               //section omitted for brevity






Objects that were learned in previous recordings are affected by the value of BeautifySavedObjects.



settings dialog, settings

·UserFunctionsPath: Path (relative to the test directory) to the file with user-defined functions utilized in this test.  Normally this file has name in form *.user.js.
·CustomStrings: Click to open the NameValue Collection Editor Dialog.
·ObjectsPath: Path (relative to the test directory) to file containing object tree information. This file contains saved_script_objects structure with all object locators gathered during recording and learning. Normally this file has name in form *.objects.js.
·ReportPath: Path (relative to the test directory) to the test's report file. Normally this file has extension form .trp which stands for Test Report.
·ScriptPath: Path (relative to the test directory) to the test script.
·TestPath: Path to the test definition file (*.sstest).