Sahi Script Editor

abstract The enhanced Sahi Script Editor (available from v6.0) is used to create, edit, refactor and run Sahi scripts, Scenarios, Suites and Data Driven Suites. It allows conversion of steps into parameterized functions and extraction of constants.

Launching the Editor

Editor can be launched by clicking on the Editor link from Sahi dashboard.

It can also be launched from the Sahi controller to edit the currently recorded script. A typical editor window will look like this.


This is the left-most panel in the editor and shows all the scripts, suites and other files in the scripts directory.

At the top of Navigator, there are three buttons. You can use them as follows:

Refresh: This button is used to refresh the directory so that newly added scripts are visible.

Link to Editor: If active, the name of script being edited will be scrolled to in the navigator menu.

Collapse: This will collapse the navigator and provide some additional space for the script editor.

Expand All: This will expand all scripts and sub-folders.

Collapse All: This will collapse all scripts and sub-folders.

The filter at the top of navigator is used to filter scripts based on the entered text. It can also be used to filter all suites and scripts.

All the scripts and suites are listed in a tree menu in the navigator. If you click on the name of a script or suite, it will open up for editing in the script editor. Also, if you right click on the name of script or suite, following menu is available.

Run: If playback properties are configured, it will start script execution. If not, it opens up the playback properties window. Once executed, scripts can be stopped by clicking on the "Stop All" button in the top menu. Open: Opens the current file. Logs: Opens the HTML logs for the current script. Docs: Opens the script in documentation mode. Rename: Makes the filename editable. Delete: Deletes the file. Cut: Cut the current file. Copy: Copy the current file. Paste: Paste the cut/copied file.

Script Editor

Script editor provides an interface to edit the Sahi scripts within a browser window. The editor integrates with function creator and context editor to provide an easy interface to refactor the scripts. To edit a script, simply select the script from the navigator and start editing in the editor. Editor provides different interfaces for scripts, scenario and suites.

Errors in Scripts

The script editor also shows if there are any errors in your scripts. It shows a red cross sign at the line containing error. If you hover on the cross sign, it shows you more detail about the error. You can click on up and down arrow to move to next or previous error.

Context Panel

Context editor provides the ability to include any function from the scritps directory to the current script and include the file containing the function. It also allows changing the Accessor Repository parameters. You can open context editor by clicking on the show context button.

Function Details

  1. Search for the function name.
  2. Select the file from which function is to be used. It is possible that same function is defined at multiple places.
  3. Provide the values for arguments.
  4. Click on Insert button to insert the function.
  5. In you want to insert the function call, end it with a semi-colon and move to next line, click on this option.
  6. You can also update the values of arguments and click on update button. This will update the values in script.
  7. If you want to open the file containing functions, you can click on Open button to open this file as a new tab.
  8. If the file containing function is not included, it shows up in red color. Click on include button to include the file.
To lookup the details of a function or Sahi API, you can CTRL+click on the name of function or API in the editor. This will open up the context editor with the details of the function or API.

Accessor Repository Details

If the script is using an Accessor Repository (AR), the AR parameters can be modified by pressing CTRL key and clicking the line of code with object. This populates the Accessor Repository parameters. One can edit the AR value. To edit the key use the Find Usage dialog.
dangerAccesor repository keys must always be in the format $_ALL_IN_CAPS. If this is not followed, the scripts will still work fine, but the values will not come up properly in Script Editor's context panel.
Click here to know more about recording with Accessor Repository.

Traversing between files while function lookup

In all the above scenarios, you can traverse between last few files using the Previous and Next button present on the top menu of editor.

Function Creator

To create a function out of the statements in a script, select the statements and then click on create function button. The following window will pop up. Provide a function name and click on continue.

You can also provide function names in userdata/config/function_names.txt file and select one of these while creating functions. This file can be edited using the Configure link on Dashboard and then selecting the file name from left navigation.


To search within a script, click inside the editor and then use either the search icon in the menu or CTRL + F to bring up the search bar.

Auto-Indentation of Scripts

Sahi Scripts can be Auto-Intended. Lets assume your original script looks like Clicking the Auto-Indentation button will beautify the script and make it more readable. NOTE: We use semi-colon as a line separator while formatting the script. Also, it will format the entire script and not selected statements.

Find and Replace

Search To search usage of a function or variable across multiple scripts, click on the Find Usage button on the top navigation bar. The following search window will appear. Provide the string to search for and click on Find button. You can also select the string from the script opened in the editor and it will set that value for search field automatically. It displays the searched results as follows: 1. Shows the number of results found for the search. The checkbox at left will select all the files. 2. Shows the name of file in which search text was found. 3. Shows the line number where search text was found.

To search for usage of a function across the scripts folders, select the checkbox for function while searching. To search for usage of a variable across the scripts folders, select the checkbox for variable while searching. If you want to perform an exact match in search, select the textbox for exact search. If you want to search in specific set of files, you can provide the regular expression pattern in File pattern. For example, if search is to be performed only in .sah files, you can use *.sah as expression.


To replace a function or variable, search for the function or variable first. Once the results of search are available, provide the string which will replace the searched text in Replace With box. Select the files in which replacement is to be done. If you want to make the change in all the files, select all files by clicking the top checkbox. Click on Replace button and Sahi will show you an alert asking if you want to actually replace. Click Yes to replace and Cancel to Cancel the operation.

Scenario Editor

Scenario file can be created in two variations in Sahi. Starting from Sahi Pro 6.1.0, a new format as shown below is introduced. This allows for adding additional columns. The example below shows two additional columns Comments and Tags added to the file.

info Additional columns can only be added before TestCase column. A column with heading as "Tags" has a special meaning and will allow you to select the tags during execution.
To edit a scenario file, just click on the file name from navigator. The CSV file is displayed in an excel like grid where it can be edited with the help of tools available to this view. In the second format, you can insert comment in column A and tags in column B. While playback, you can provide the tags as an expression using binary operators. Sahi will evaluate the expression and run the scenarios which qualify the condition in tags.

In the image above, the scenarios with 'admin' OR 'customer' tag AND with 'smoke' tag will be filtered out and executed. Following tools are available while editing a scenario file.

1. Insert Testcase: Inserts a blank test case 2. Load Sahi library: Inserts the syntax to include a function library. You can press CTRL and click on the name of included file to open it up in a new tab of editor. 3. Function details: Shows all the details about the function that was selected before cliking the button. It shows all the files containing the function. If the file containing the function is not included, you can click on the include button to include the file. You can also press CTRL and click on the function name to see it's details. 4. Import: Imports functions to the csv. Enter the functions that you want to import in the text area with proper arguments. Click on the import button to insert the functions in the scenario file.

Documentation tool

Sahi can be used as a documentation tool as well. While scripts can be recorded in documentation mode, documentation for already existing scripts can be generated by clicking on View Doc button. A new tab will open where the documentation can be edited and exported as HTML


Script Editor enables playback of scripts/suites/data driven suites. Scripts can be played back on a single machine or distributed across machines.

To configure playback properties, click on the Playback button in the top menu. It opens up the basic configurations required for the script execution.

Based on the playback properties set by the user, Sahi will execute the appropriate script or suite.

At the very minimum, you need to provide a start mode, start URL and browser name to execute the script. Script directory and script file fields show the file for which play button was clicked.

  1. Select appropriate Start Mode to run a script.
    infoNote: Start Mode is only avilable when Sahi Pro Desktop Add-on is installed.
    • Desktop Browser mode is used to run a script which runs on desktop browser only.
    • Windows mode is used to run a script which runs on windows for desktop only.
    • Generic mode is used to run a script when _setMode already defined in the script.
  2. Select the browser from the dropdown. This lists all the browsers configured on your machine. In case you are providing multiple nodes for distributed playback, this will list browsers from all nodes. One can choose more than one browser to run the script/suite in.
  3. Enter the Start URL.
  4. Click on the Play button to play the script. The default setup (Run in parallel with Threads as 5) lets you run the scripts in parallel with 5 simultaneous instances.
  5. If you wish to run the scripts in the suite one after another within the same browser session, select "Run sequentially in single browser session". This will open a browser window and execute scripts one after the other on this same browser window. The browser window will only be closed at the end of the suite. Use this with caution.
  6. If you wish to run the scripts in the suite one after another but in different browser sessions, select "Run in parallel" with Threads as 1. Browser window will be closed after each script.

Distributed Playback

Playback properties can be configured to distribute script execution across multiple machines.
  1. To distribute the playback across multiple machines, check the Run distributed radio button.
  2. Click on the button to configure nodes for playback.
  3. Provide the machine names and port numbers.
  4. To use the node for execution, check the "Use" checkbox for the node. (Sometimes you may may want to exclude 1 or 2 nodes from the nodes list. You can uncheck that particular node without deleting the entry.)
  5. Click on Update button. This updates the node information for execution.
  6. Click on Close button to close the node configuration window.
  7. This allows you to add more space for additional nodes.
  8. Set the number of threads to be executed on each Node
After configuring the nodes, you can click on play to execute the script or suite across machines.

Using a Different Master

  1. By default Sahi will consider the localhost as the master node. If you want to use a different master, click the checkbox for Use Different Master.
  2. Provide the machine name to be used as the host.
  3. Provide the port (default 9999).

Advanced Playback Settings

While setting playback properties, following advanced settings can be configured by clicking on the "Show Advanced Settings" link.

  1. Offline Reports: You can configure the storage of offline logs by setting the paths for various types of reports.
    1. Click on the button to bring up the Logs Info Editor.
    2. Provide the location for storing the logs.
    3. Unless you click on Use, the settings won't be considered. Click the Use checkbox for the type of logs that you want.
    4. Click on update to update the Offline logs settings.
    5. Once updated, you can close the Logs Info Editor.
  2. Show Periodic Summary You can get a regular update of the suite status by enabling Show Periodic Summary. If the script is being played back from the Editor itself, the regular updates appear on the bottom right corner of the screen. This functionality is also updated in the sample Ant file. You can read more about it here.
  3. Send Email Reports: You can enable sending email reports after script run on Success, Failure or both.
    1. Click on the checkbox to enable sending email reports.
    2. Select the trigger for sending email reports. It can be either success or failure or both.
    3. Periodic emails: For a long running suite, users can configure emails to be sent periodically while the suite run is in progress. Click on checkbox for sending out periodic emails. In the dropdown below, select the time interval at which the email should be sent.
    4. Sahi uses the properties file present at userdata/config/ to send the emails. You can click on this button to edit the file. You can change the properties file using other text editor as well.
    5. danger The user needs to edit the and set the various properties. By default, none of the properties are set.
  4. Extra Parameters: You can pass extra parameters to script or suite before playback in form of key value pairs. These values can then be used within the scripts.
    1. Click on the button to open Extra Param Editor.
    2. Provide the name and value for the parameters.
    3. Click on Mask checkbox to hide the values of parameters from logs. This is useful for masking information like passwords.
    4. Update button populates the parameters and their values in Extra Parameters text box. This will be then passed on to the script.
    5. Click on close to close the Extra Param Editor.
    6. If you would like extra space for parameters, you can click the button to add an extra row.
  5. User Defined Id: You can provide a unique ID to be used as User Defined Id for the script//suite run. This can be displayed in any type of log by changing
    <xsl:param name="showUserDefinedId" select="'false'" />
    <xsl:param name="showUserDefinedId" select="'true'" />
    in the suites_list.xsl of userdata\config\reports\. can be html, xml etc

Scheduling a Test

Tests can be scheduled to be executed on a future date using the Editor. To schedule the a script, open playback properties for the script and hover on the Run button. Click Schedule button from the dropdown.
  1. Choose a date and time from the dropdown. Click OK to set the date.
  2. Provide a description(optional) for the test.
  3. Click on Schedule to schedule the test.
Once scheduled, you will receive the above confirmation on the editor at the bottom right corner.

Creating suites

You can select scripts from the navigator and select Suite or Data driven suite from the Create Suite Dropdown at top. This will create a new suite which consists of the selected scripts.

Creating Accessor Repository

AR can be created for selected scripts from the navigator by clicking on Create AR button at top. In case no scripts are selected, AR will be created for currently opened script. In case you want to revert back the action, you can find scripts backup in userdata -> scripts_backup folder. The scripts_backup folder contains scripts backup. You can simply copy the folders in scripts_backup folder and paste in userdata -> scripts folder to revert back the action.
infoPlease make sure that you have read and write permission for sahipro/userdata folder in userdata/config/ file

Editor Shortcuts

Shortcut Explanation
CTRL + S Save current file
ALT + Up Arrow Move current line up
Alt + Down Arrow Move current line down
CTRL + D Delete the current line
CTRL + F Search in script
CTRL + / Comment selected lines
CTRL + ALT + Up Arrow Copy current line above
CTRL + ALT + Down Arrow Copy current lown on next line
CTRL + L Opens a dialog box to enter line number. Enter line number and press enter to go to line.

Debugging Sahi Scripts

You can add breakpoints in your script before playback by clicking near the line number on the left of the script editor. A red dot appears to indicate the breakpoint. In the following image, 1 and 2 are the breakpoints. The breakpoints will only be considered when the script is executed in the debug mode. To execute in debug mode, select the Debug option from the dropdown next to Run button in Script Editor.

When that script is executed from the editor, it will reach the breakpoint and pause the playback. Sahi controller will launch at that point and then you can go to playback tab and either step over next lines or click on play to resume playback. 1. In the above image, the script is paused at breakpoint number 1. 2. Click on step to execute next statement.

To clear all breakpoints across all scripts, you can click the 'clear all breakpoints' button in the script editor. This button can be found in the top menu.

danger When run in debug mode, the script will wait indefinetly at the breakpoint unless you click play from the controller or press step to step through next steps.

Password Encoder

You can encode you password from editor for using in scripts. 1. In the above image, type the password. 2. Click on generate to get the encoded password.

Now you can use the encoded password in _setPassword Api.
info You can change the salt by changing the property script.salt_for_password_encryption in userdata/config/ file.