Launchers / Automated tests

Sahi 3.5 Launcher (sahi35.jar)

The Sahi 3.5 launcher allows interfacing with Sahi 3.5 (.sah) scripts.
It has been tested with Sahi v3.5.
The only difference with the Sahi 3 Launcher is the way to start the tests (because the command line has been slightly modified to support test, browserType, baseUrl and host option).

Process

  • Each test in XStudio must have his dedicated .sah script. The name of the script MUST be equal to the name of the test.
  • The sahi proxy server is launched by the launcher using this syntax:
    "<javaInstallPath>/bin/java.exe" -cp ../../lib/sahi.jar;../../extlib/rhino/js.jar;
    ../../extlib/apc/commons-codec-1.3.jar net.sf.sahi.Proxy ../.. ..
    or with Sahi Pro:

    "<javaInstallPath>/bin/java.exe" -cp ../../lib/sahi.jar;../../extlib/rhino/js.jar;
    ../../extlib/apc/commons-codec-1.3.jar;../../extlib/db/h2-1.2.134.jar;
    ../../extlib/license/truelicense.jar;
    ../../extlib/license/truexml.jar
    net.sf.sahi.Proxy ../.. ..
    and from the working directory "<sahiInstallPath>/userdata/bin"
  • The utility tool to enable proxying on the browser is launched.
  • The sahi test runner is launched by the launcher using this syntax:
    "<javaInstallPath>/bin/java.exe" -cp ../../lib/ant-sahi.jar net.sf.sahi.test.TestRunner
    -test "<testRootPath>/<testPath>/<testName>.sah"
    -browserType "<browserExePath>"
    -baseUrl <baseUrl>/<additionalInfo>
    -host localhost 9999 3 <processName> "<option>"
    and from the working directory "<sahiInstallPath>/userdata/bin"
  • The utility tool to disable proxying on the browser is launched.


Permissions

WARNING: if you're running your tests on Windows, it may be required to run the tests as administrator.
Having an account with Administrators permissions may even not be enough in some cases (especially if you're using Windows 10) and you may need to disable completely the UAC (User Access Control) on your computer.
To do so:
  • Press the Windows + R key combination
  • Type in regedit
  • Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
  • In the right-side pane, look for EnableLUA and set the value 0
  • Close the registry editor
  • Restart your computer

Debug

If your tests are not executed correctly or are reporting only failures, this is very likely because your configuration is incorrect or because you used a wrong naming convention for your tests and test cases.

The best way to quickly find out what's wrong is to look at the traces generated by XStudio (or XAgent).
The traces always include the detailed description of what the launcher performs (command line execution, script execution, API calling etc.) to run a test case. So, if you experiment some problems, the first thing to do is to activate the traces and look at what's happening when you run your tests.

Then, try to execute manually in a cmd box the exact same commands.
This will normally fail the same way.
At this point, you needs to figure out what has to be changed in these commands in order to have them run properly.

When you have something working, compare these commands to what's described in the Process chapter above. This will tell you exactly what you need to change.

Most of the time, this is related to:
  • some incorrect values in some parameters of your configuration,
  • the name of your tests,
  • the name of your test cases,
  • the canonical path of your tests