Skip to content
Sahi Pro Flowcharts is retired. These pages document the last release (v12) and are no longer updated. Go to the current documentation.Flowcharts is retired. Current docs
Get Free Trial
Sahi Pro Flowcharts is retired. These pages document the last release (v12) and are no longer updated. Go to the current documentation.

Playback via Command Line

During development, paths will be played back from the Run Settings dialog. For Continuous Integration systems, create an ANT target and trigger from there. This section describes a way of triggering paths from the command line via bat files or shell scripts.

flowcharts_testrunner.bat and flowcharts_testrunner.sh files allow running paths from the command line.

  1. Open a command prompt and cd to sahi/userdata/bin (or click on the “Bin” link on the Sahi Dashboard)

  2. Run flowcharts_testrunner.bat to see the syntax

    D:\sahi_pro\userdata\bin>flowcharts_testrunner.bat
    --
    Usage: flowcharts_testrunner.bat <Project Name> <FlowChart Name> <Path Id> <startURL> <browserType|browserDeviceParams> <tags> <Run Type> <Extra Parameters>
    Project Name is relative to userdata/scripts/flowchartsdata
    Multiple browsers can be specified using +. Eg. firefox+chrome
    browserDeviceParams can be specified as the combinations of StartMode, Browser, AndroidDevice and iOSDevice
    Eg. "Browser:chrome;AndroidDevice:XXXX;iOSDevice:YYYY;StartMode:BROWSER"
    test cases can be specified in tags argument as "testcases:testcase1,testcase2"
    Run Type can be specified as the combinations of Normal, Positive, Negative
    Eg. "true;true;true"
    Give absolute path of extra parameters file
    --
    Example:
    flowcharts_testrunner.bat "1. Open Cart Basic" "" "" https://demoapps.testflowchart.com/oc/ chrome
    flowcharts_testrunner.bat "1. Open Cart Basic" "" "" https://demoapps.testflowchart.com/oc/ firefox
    flowcharts_testrunner.bat "1. Open Cart Basic" "" "" https://demoapps.testflowchart.com/oc/ firefox+chrome
    flowcharts_testrunner.bat "1. Open Cart Basic" "Registration" "" https://demoapps.testflowchart.com/oc/ chrome
    flowcharts_testrunner.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome
    flowcharts_testrunner.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome "" "true"
    flowcharts_testrunner.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome "" "true;true"
    flowcharts_testrunner.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome "" "true;true;true"
    flowcharts_testrunner.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome "" "" "scripts/extraParameters.properties"
    flowcharts_testrunner.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome "all"
    flowcharts_testrunner.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome "win||all"
    flowcharts_testrunner.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome "(user||admin)&&medium"
    flowcharts_testrunner.bat "3. Checkout with Preconditions" "Create Product" "0" https://demoapps.testflowchart.com/oc/ chrome "testcases:TC_CreateProduct_WithValidData"
    flowcharts_testrunner.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ "AndroidDevice:xyz;StartMode:ANDROID"
    flowcharts_testrunner.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ "AndroidDevice:xyz;StartMode:ANDROID_BROWSER"
    flowcharts_testrunner.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ "iOSDevice:abc;StartMode:IOS"
    flowcharts_testrunner.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ "iOSDevice:abc;StartMode:IOS_BROWSER"
    flowcharts_testrunner.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ "AndroidDevice:xyz;iOSDevice:abc;StartMode:GENERIC"
    flowcharts_testrunner.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ "Browser:chrome;StartMode:WINDOWS"
    flowcharts_testrunner.bat "1. Open Cart Basic" "Registration" "0" " " "StartMode:WINDOWS"
    flowcharts_testrunner.bat "1. Open Cart Basic" "Registration" "0" " " "StartMode:JAVA"
    flowcharts_testrunner.bat "1. Open Cart Basic" "Registration" "0" " " "StartMode:SAP"
    --
    D:\sahi_pro\userdata\bin>
  3. Parameters other than project name, flowchart name, path id, startURL and browserType, tags, run type, extra parameters can be modified by editing flowcharts_testrunner.bat

    1. To set the number of parallel browsers to execute the paths in, modify

      SET THREADS=5

      To run in one thread only, i.e. to run paths one after the other sequentially, use

      SET THREADS=1
    2. Sahi normally opens and closes the browser for each path. To execute all path sequentially without closing and reopening browsers, use

      SET THREADS=1
      SET SINGLE_SESSION=true
    3. Sahi, by default, writes logs to the database only. To force it to write logs to the filesystem, use

      SET LOGS_INFO=html,xml

      html and xml logs will be created in the sahi/userdata/logs/playback folder

      To force it to write logs to specific file locations, use,

      SET LOGS_INFO=html:D:/reports/htmllogs/,xml:D:/reports/xmllogs/

      Output formats available are html,xml,junit,excel,pdf

      The format to specify LOGS_INFO is

      reportType1:filePath1,reportType2,reportType3:filePath3,...
    4. When a path is run, some paths may fail because of environment reasons or due to browser crashes. A natural next step for testers is to verify the failure by running the path again. Sahi now automatically creates a suite of all failed paths. For example if you ran a project 1. Open Cart Basic on Firefox, failed suite will be created as 1. Open Cart Basic_failed_firefox.flowcharts.dd.csv

      This failed suite file can then be run to verify only the failed testcases.

    5. Sahi can send out emails at the end of a path run. Set the following properties in flwocharts_testrunner.bat file.

      SET SEND_EMAIL_REPORT=true
      SET EMAIL_TRIGGER=success,failure
      SET EMAIL_PROPERTIES=email.properties
      SET EMAIL_PASSWORD_HIDDEN=true

      Email specific parameters like username, password etc. are defined in sahi/userdata/bin/email.properties file.

    6. For a long-running projects, Sahi can send periodic emails indicating progress. To enable periodic emails, set the following property in flowcharts_testrunner.bat file.

      SET SEND_EMAIL_REPORT_PERIODICALLY=true

      To set time interval (in minutes), set the following property in flowcharts_testrunner.bat file.

      SET SEND_EMAIL_REPORT_PERIODICALLY_TIME=30
    7. Custom fields can be passed to the scripts using the CUSTOM_FIELDS variable. More than one custom field can be passed. Replace the custom field keys and values as appropriate.

      For Windows:

      SET CUSTOM_FIELDS=-customField customValue -anotherCustomField "another value"

      For Linux:

      Terminal window
      export CUSTOM_FIELDS="-customField customValue -anotherCustomField another value"
    8. Sahi Pro v6.3.0 onwards, a summary of the paths playback status is written to the Flowcharts_Testrunner console while the path is running. You can read more on Periodic Summary here.

      To disable these messages in Windows, set the following property in flowcharts_testrunner.bat file.

      SET SHOW_PERIODIC_SUMMARY=false

      For Mac and Linux, you need to set the following property in flowcharts_testrunner.sh

      Terminal window
      export SHOW_PERIODIC_SUMMARY=false

Sahi Pro can distribute and run tests on multiple machines (nodes). The machine which distributes the scripts and manages the distributed run is referred to as the Master. All Dashboard logs are visible from the Master. The other machines are called Slaves. Any machine in the distributed environment can serve as the Master. The machine which launches the distributed run is referred to as the Initiator. Sahi provides a couple of batch files - flowcharts_drun.bat and flowcharts_drun_different_master.bat (and equivalent shell scripts). They allow running test scripts on multiple machines from the command line.

  • flowcharts_drun.bat should be used when the Master and Initiator are the same machine.
  • flowcharts_drun_different_master.bat should be used when the Master is different from the Initiator.
  1. Sahi distributes the scripts to different machines based on their capacity and availability of browsers. Note that Sahi should be running on each of the nodes. Also, on each machine, the browser paths must be correctly specified.

  2. Open sahi_pro/userdata/bin/flowcharts_drun.bat (flowcharts_drun.sh on linux) using any editor.

  3. SOURCE_SCRIPTS_PATH points to the folder that contains ALL the scripts to be run. It should be relative to sahi_pro/userdata folder OR it should be an absolute path.

    For Windows:

    SET SOURCE_SCRIPTS_PATH=..\scripts

    For Linux:

    Terminal window
    export SOURCE_SCRIPTS_PATH=../scripts
  4. Configure the NODES variable to contain all the machines on which the tests should run. The command to set the nodes in Windows and Linux respectively are: For Windows:

    SET NODES=localhost:9999,othermachine:9999,thirdmachine:9999

    For Linux:

    Terminal window
    export NODES=localhost:9999,othermachine:9999,thirdmachine:9999
  5. From Sahi Pro 6.1.0 onwards, it is possible to specify the number of threads that the paths of the project would run in. The number of maximum parallel browsers would be the minimum of two values - threads, and capacity of the browser specified in browser_types.xml.

    To set the number of parallel browsers to execute the paths in, modify

    SET THREADS=5

    To run in one thread only, i.e. to run paths one after the other sequentially, use

    SET THREADS=1

    Note that this would affect the number of parallel browsers on each Node.

  6. When a path is run, some paths may fail because of environment reasons or due to browser crashes. A natural next step for testers is to verify the failure by running the path again. Sahi now automatically creates a suite of all failed paths. For example if you ran a project 1. Open Cart Basic on Firefox, failed suite will be created as 1. Open Cart Basic_failed_firefox.flowcharts.dd.csv

    This failed suite file can then be run to verify only the failed scripts.

  7. Sahi can send a mail summarizing the playback. The variable SEND_EMAIL_REPORT can be set as true or false. If true, Sahi sends the mail.

    For Windows:

    SET SEND_EMAIL_REPORT=true

    For Linux:

    Terminal window
    export SEND_EMAIL_REPORT=true
  8. Sahi can send a mail based on success or failure or in both the cases. This condition can be set using the EMAIL_TRIGGER variable.

    For Windows:

    SET EMAIL_TRIGGER=success,failure

    For Linux:

    Terminal window
    export EMAIL_TRIGGER=success,failure
  9. For a long-running project, Sahi can send periodic emails indicating progress. To enable periodic emails, set the following property.

    For Windows:

    SET SEND_EMAIL_REPORT_PERIODICALLY=true

    For Linux:

    Terminal window
    export SEND_EMAIL_REPORT_PERIODICALLY=true

    To set time interval (in minutes), use SET SEND_EMAIL_REPORT_PERIODICALLY_TIME variable.

    For Windows:

    SET SEND_EMAIL_REPORT_PERIODICALLY_TIME=30

    For Linux:

    Terminal window
    export SEND_EMAIL_REPORT_PERIODICALLY_TIME=30
  10. The relative path to the properties file containing information about the mail such as sender, recipient, host, port etc. can be set using the EMAIL_PROPERTIES variable.

  11. Passwords can be hidden or shown from the console and logs by toggling the EMAIL_PASSWORD_HIDDEN variable. It can be set as true or false. If true, Sahi hides the password from Sahi console and logs.

  12. Custom fields can be passed to the scripts using the CUSTOM_FIELDS variable. More than one custom field can be passed. Replace the custom field keys and values as appropriate.

    For Windows:

    SET CUSTOM_FIELDS=-customField customValue -anotherCustomField "another value"

    For Linux:

    Terminal window
    export CUSTOM_FIELDS="-customField customValue -anotherCustomField another value"
  13. The end user can pass a specific id for each run using the USER_DEFINED_ID variable.

    For Windows:

    SET USER_DEFINED_ID=-userDefinedId "Some Id"

    For Linux:

    Terminal window
    export USER_DEFINED_ID="-userDefinedId Some Id"

    Replace the value “Some Id” as appropriate.

  14. Sahi can set offline logs to be generated in xml, html, pdf, junit and excel types. The default type is html.

    For Windows:

    SET LOGS_INFO=xml,html

    For Linux:

    Terminal window
    export LOGS_INFO=xml,html
  15. Sahi Pro v6.3.0 onwards, a summary of the path playback status is written to the Flowcharts_Drun console while the path is running. You can read more on Periodic Summary here.

    To disable these messages in Windows, set the following property in flowcharts_drun.bat file.

    SET SHOW_PERIODIC_SUMMARY=false

    For Mac and Linux, you need to set the following property in flowcharts_drun.sh

    Terminal window
    export SHOW_PERIODIC_SUMMARY=false
  16. To execute the path using flowcharts_drun.bat, open a command window and go to the <sahi_home>/userdata/bin directory. This can also be done easily by clicking the bin link on the dashboard.

  17. Run flowcharts_drun.bat to see the syntax.

    D:\sahi_pro\userdata\bin>flowcharts_drun.bat
    --
    NOTE: Use this batch file only if you are running it on the Master machine. If you wish to use a different Master, use flowcharts_drun_different_master.bat instead.
    --
    Usage: flowcharts_drun.bat <Project Name> <FlowChart Name> <Path Id> <startURL> <browserType|browserDeviceParams> <tags> <Run Type> <Extra Parameters>
    Project Name is relative to userdata/scripts/flowchartsdata
    Multiple browsers can be specified using +. Eg. firefox+chrome
    browserDeviceParams can be specified as the combinations of StartMode, Browser, AndroidDevice and iOSDevice
    Eg. "Browser:chrome;AndroidDevice:XXXX;iOSDevice:YYYY;StartMode:BROWSER"
    test cases can be specified in tags argument as "testcases:testcase1,testcase2"
    Run Type can be specified as the combinations of Normal, Positive, Negative
    Eg. "true;true;true"
    Give absolute path of extra parameters file
    --
    Example:
    flowcharts_drun.bat "1. Open Cart Basic" "" "" https://demoapps.testflowchart.com/oc/ chrome
    flowcharts_drun.bat "1. Open Cart Basic" "" "" https://demoapps.testflowchart.com/oc/ firefox
    flowcharts_drun.bat "1. Open Cart Basic" "" "" https://demoapps.testflowchart.com/oc/ firefox+chrome
    flowcharts_drun.bat "1. Open Cart Basic" "Registration" "" https://demoapps.testflowchart.com/oc/ chrome
    flowcharts_drun.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome
    flowcharts_drun.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome "" "true"
    flowcharts_drun.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome "" "true;true"
    flowcharts_drun.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome "" "true;true;true"
    flowcharts_drun.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome "" "" "scripts/extraParameters.properties"
    flowcharts_drun.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome "all"
    flowcharts_drun.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome "win||all"
    flowcharts_drun.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome "(user||admin)&&medium"
    flowcharts_drun.bat "3. Checkout with Preconditions" "Create Product" "0" https://demoapps.testflowchart.com/oc/ chrome "testcases:TC_CreateProduct_WithValidData"
    flowcharts_drun.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ "AndroidDevice:xyz;StartMode:ANDROID"
    flowcharts_drun.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ "AndroidDevice:xyz;StartMode:ANDROID_BROWSER"
    flowcharts_drun.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ "iOSDevice:abc;StartMode:IOS"
    flowcharts_drun.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ "iOSDevice:abc;StartMode:IOS_BROWSER"
    flowcharts_drun.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ "AndroidDevice:xyz;iOSDevice:abc;StartMode:GENERIC"
    flowcharts_drun.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ "Browser:chrome;StartMode:WINDOWS"
    flowcharts_drun.bat "1. Open Cart Basic" "Registration" "0" " " "StartMode:WINDOWS"
    flowcharts_drun.bat "1. Open Cart Basic" "Registration" "0" " " "StartMode:JAVA"
    flowcharts_drun.bat "1. Open Cart Basic" "Registration" "0" " " "StartMode:SAP"
    --
    D:\sahi_pro\userdata\bin>

This should be used when the Master is different from the Initiator. A typical case where you would use this or the ANT equivalent, is when you have a continuous integration build server that is not capable of launching any UI. The build server will contain all the scripts but since it cannot launch any UI, it cannot run Sahi tests. In such a case, Sahi can be run on other machines and flowcharts_drun_different_master can be used on the integration build server to trigger the Sahi tests on these machines.

flowcharts_drun_different_master does the following.

  • It first creates script for the given project/flowchart/path and syncs the contents generated scripts folder from the Initiator to a staging folder on the Master.
  • It then distributes the scripts from the staging folder of the Master to various nodes and runs the tests.
  • If offline logs are requested, the logs are copied over from the Master to the Initiator after the run is over.

Let us look at flowcharts_drun_different_master in more detail.

  1. Sahi (running on the Master) distributes the scripts to different machines based on their capacity and availability of browsers. Note that Sahi should be running on each of the nodes. Also, on each machine, the browser paths must be correctly specified.

  2. The following directory structure is assumed on the Initiator machine. The requisite files like ant-sahi.jar should be copied over from a Sahi Pro installation. The directory structure of the files is the same in the SahiPro installation.

    <TOP_LEVEL_FOLDER>
    lib
    ant-sahi.jar
    logs
    userdata
    bin
    flowcharts_drun_different_master.bat
    setjava.bat
    config
    email.properties
    scripts
    <ALL YOUR SCRIPT FOLDERS AND SCRIPTS>
  3. Open <sahi_home>/userdata/bin/flowcharts_drun_different_master.bat (flowcharts_drun_different_master.sh on linux) using any Editor.

  4. MASTER_HOST should point to the Master machine. For Windows:

    SET MASTER_HOST=machine2

    For Linux:

    Terminal window
    export MASTER_HOST=machine2
  5. INITIATOR_ORIGIN_FOLDER is the path to the base folder containing the various scripts. With the above assumed directory structure, it would point to <TOP_LEVEL_FOLDER>/userdata/scripts.

  6. MASTER_STAGING_PATH refers to the Staging folder on the Master machine to which the contents of INITIATOR_ORIGIN_FOLDER will be first synced to. Distribution of scripts will happen from MASTER_STAGING_PATH.

  7. Configure the NODES variable to contain all the machines on which the tests should run. The command to set the nodes in Windows and Linux respectively are: For Windows:

    SET NODES=machine2:9999,machine3:9999,machine4:9999

    For Linux:

    Terminal window
    export NODES=machine2:9999,machine3:9999,machine4:9999
  8. From Sahi Pro 6.1.0 onwards, it is possible to specify the number of threads that the paths would run in. The number of maximum parallel browsers would be the minimum of two values - threads, and capacity of the browser specified in browser_types.xml.

    To set the number of parallel browsers to execute the path in, modify

    SET THREADS=5

    To run in one thread only, i.e. to run paths one after the other sequentially, use

    SET THREADS=1

    Note that this would affect the number of parallel browsers on each Node.

  9. When a path is run, some paths may fail because of environment reasons or due to browser crashes. A natural next step for testers is to verify the failure by running the path again. Sahi now automatically creates a suite of all failed paths. For example if you ran a project 1. Open Cart Basic on Firefox, failed suite will be created as 1. Open Cart Basic_failed_firefox.flowcharts.dd.csv

    This failed suite file can then be run to verify only the failed scripts.

  10. Sahi can send a mail summarizing the playback. The variable SEND_EMAIL_REPORT can be set as true or false. If true, Sahi sends the mail. For Windows:

    SET SEND_EMAIL_REPORT=true

    For Linux:

    Terminal window
    export SEND_EMAIL_REPORT=true
  11. Sahi can send a mail based on success or failure or in both the cases. This condition can be set using the EMAIL_TRIGGER variable. For Windows:

    SET EMAIL_TRIGGER=success,failure

    For Linux:

    Terminal window
    export EMAIL_TRIGGER=success,failure
  12. For a long-running projects, Sahi can send periodic emails indicating progress. To enable periodic emails, set the following property.

    For Windows:

    SET SEND_EMAIL_REPORT_PERIODICALLY=true

    For Linux:

    Terminal window
    export SEND_EMAIL_REPORT_PERIODICALLY=true

    To set time interval (in minutes), use SET SEND_EMAIL_REPORT_PERIODICALLY_TIME variable.

    For Windows:

    SET SEND_EMAIL_REPORT_PERIODICALLY_TIME=30

    For Linux:

    Terminal window
    export SEND_EMAIL_REPORT_PERIODICALLY_TIME=30
  13. The relative path to the properties file containing information about the mail such as sender, recipient, host, port etc. can be set using the EMAIL_PROPERTIES variable.

  14. Passwords can be hidden or shown from the console and logs by toggling the EMAIL_PASSWORD_HIDDEN variable. It can be set as true or false. If true, Sahi hides the password from Sahi console and logs.

  15. Custom fields can be passed to the scripts using the CUSTOM_FIELDS variable. More than one custom field can be passed. Replace the custom field keys and values as appropriate. For Windows:

    SET CUSTOM_FIELDS=-customField customValue -anotherCustomField "another value"

    For Linux:

    Terminal window
    export CUSTOM_FIELDS=-customField customValue -anotherCustomField "another value"
  16. The end user can pass a specific id for each run using the USER_DEFINED_ID variable. For Windows:

    SET USER_DEFINED_ID=-userDefinedId "Some Id"

    For Linux:

    Terminal window
    export USER_DEFINED_ID=-userDefinedId "Some Id"

    Replace the value “Some Id” as appropriate.

  17. Sahi can set offline logs to be generated in xml, html, pdf, junit and excel types. The default type is html. These logs will be generated on the Master and pulled back to the Initiator, since the user would want to see the logs on the Initiator. The following set of commands illustrate how HTML and XML logs can be generated.

    For Windows:

    SET UNIQUE_ID=%DATE%__%TIME%
    SET UNIQUE_ID=%UNIQUE_ID: =_%
    SET UNIQUE_ID=%UNIQUE_ID::=_%
    SET UNIQUE_ID=%UNIQUE_ID:/=_%
    SET MASTER_HTMLLOGS_DIR=logs/temp/html/%UNIQUE_ID%
    SET MASTER_XMLLOGS_DIR=logs/temp/xml/%UNIQUE_ID%
    SET LOGS_INFO=html:%MASTER_HTMLLOGS_DIR%,xml::%MASTER_XMLLOGS_DIR%
    SET INITIATOR_OUTPUT_HTMLLOGS_DIR=%TOP_LEVEL_FOLDER%/logs/html/%UNIQUE_ID%
    SET INITIATOR_OUTPUT_XMLLOGS_DIR=%TOP_LEVEL_FOLDER%/logs/xml/%UNIQUE_ID%

    For Linux:

    Terminal window
    export UNIQUE_ID=$(date +"%m_%d_%Y")__$(date +"%I_%M_%S")
    export MASTER_HTMLLOGS_DIR=logs/temp/html/$UNIQUE_ID
    export MASTER_XMLLOGS_DIR=logs/temp/xml/$UNIQUE_ID
    export LOGS_INFO=html:$MASTER_HTMLLOGS_DIR,xml:$MASTER_XMLLOGS_DIR
    export INITIATOR_OUTPUT_HTMLLOGS_DIR=$TOP_LEVEL_FOLDER/logs/html/$UNIQUE_ID
    export INITIATOR_OUTPUT_XMLLOGS_DIR=$TOP_LEVEL_FOLDER/logs/xml/$UNIQUE_ID
  18. Sahi Pro v6.3.0 onwards, a summary of the playback status is written to the FlowCharts_Drun_Different_Master console while the script is running. You can read more on Periodic Summary here.

    To disable these messages in Windows, set the following property in flowcharts_drun_different_master.bat file.

    SET SHOW_PERIODIC_SUMMARY=false

    For Mac and Linux, you need to set the following property in flowcharts_drun_different_master.sh

    Terminal window
    export SHOW_PERIODIC_SUMMARY=false
  19. To execute the paths using flowcharts_drun_different_master.bat, open a command window and go to the <sahi_home>/userdata/bin directory. This can also be done easily by clicking the bin link on the dashboard.

  20. Run flowcharts_drun_different_master.bat to see the syntax.

    D:\sahi_pro\userdata\bin>flowcharts_drun_different_master.bat
    --
    NOTE: Use this batch file only if you plan to use a different Master machine. Else, use flowcharts_drun.bat instead.
    --
    Usage: flowcharts_drun_different_master.bat <Project Name> <FlowChart Name> <Path Id> <startURL> <browserType|browserDeviceParams> <tags> <Run Type> <Extra Parameters>
    Project Name is relative to userdata/scripts/flowchartsdata
    Multiple browsers can be specified using +. Eg. chrome+firefox
    browserDeviceParams can be specified as the combinations of StartMode, Browser, AndroidDevice and iOSDevice
    Eg. "Browser:chrome;AndroidDevice:XXXX;iOSDevice:YYYY;StartMode:BROWSER"
    test cases can be specified in tags argument as "testcases:testcase1,testcase2"
    Run Type can be specified as the combinations of Normal, Positive, Negative
    Eg. "true;true;true"
    Give absolute path of extra parameters file
    --
    Example:
    flowcharts_drun_different_master.bat "1. Open Cart Basic" "" "" https://demoapps.testflowchart.com/oc/ chrome
    flowcharts_drun_different_master.bat "1. Open Cart Basic" "" "" https://demoapps.testflowchart.com/oc/ firefox
    flowcharts_drun_different_master.bat "1. Open Cart Basic" "" "" https://demoapps.testflowchart.com/oc/ firefox+chrome
    flowcharts_drun_different_master.bat "1. Open Cart Basic" "Registration" "" https://demoapps.testflowchart.com/oc/ chrome
    flowcharts_drun_different_master.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome
    flowcharts_drun_different_master.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome "" "true"
    flowcharts_drun_different_master.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome "" "true;true"
    flowcharts_drun_different_master.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome "" "true;true;true"
    flowcharts_drun_different_master.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome "" "" "scripts/extraParameters.properties"
    flowcharts_drun_different_master.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome "all"
    flowcharts_drun_different_master.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome "win||all"
    flowcharts_drun_different_master.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ chrome "(user||admin)&&medium"
    flowcharts_drun_different_master.bat "3. Checkout with Preconditions" "Create Product" "0" https://demoapps.testflowchart.com/oc/ chrome "testcases:TC_CreateProduct_WithValidData"
    flowcharts_drun_different_master.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ "AndroidDevice:xyz;StartMode:ANDROID"
    flowcharts_drun_different_master.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ "AndroidDevice:xyz;StartMode:ANDROID_BROWSER"
    flowcharts_drun_different_master.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ "iOSDevice:abc;StartMode:IOS"
    flowcharts_drun_different_master.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ "iOSDevice:abc;StartMode:IOS_BROWSER"
    flowcharts_drun_different_master.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ "AndroidDevice:xyz;iOSDevice:abc;StartMode:GENERIC"
    flowcharts_drun_different_master.bat "1. Open Cart Basic" "Registration" "0" https://demoapps.testflowchart.com/oc/ "Browser:chrome;StartMode:WINDOWS"
    flowcharts_drun_different_master.bat "1. Open Cart Basic" "Registration" "0" " " "StartMode:WINDOWS"
    flowcharts_drun_different_master.bat "1. Open Cart Basic" "Registration" "0" " " "StartMode:JAVA"
    flowcharts_drun_different_master.bat "1. Open Cart Basic" "Registration" "0" " " "StartMode:SAP"
    --
    D:\sahi_pro\userdata\bin>

Next: Reports