TestOptimal Launcher (testoptimal.jar)

The TestOptimal launcher allows interfacing with TestOptimal tests.



Configuration

The testoptimal.xml file is just a template and must NOT be edited. It's used by the system to build dynamically the form that the user will be able to fill in from the GUI when creating a custom execution configuration.


Parameter Description
Connection
TestOptimal Server URL This must indicate the URL of the TestOptimal server.
If you'e running your tests locally, just leave the default value.

Default value is: http://localhost:8888/
User (opt.) User id to use if you enabled authentication on your TestOptimal server.

Default value is: <empty>
Password (opt.) Password to use if you enabled authentication on your TestOptimal server.

Default value is: <empty>
Execution
Sequencer This must indicate the sequencing algorithm or mode that you want to execute the model.
There are choices between:
  • OptimalSequence
  • RandomSequence
  • GreedySequence
  • MCaseSerial
  • MCaseOptimal
  • ConcurrentSequence
  • MutantPath
  • PriorityPath

Default value is: OptimalSequence
Browser This must indicate the browser to execute the model.
There are choices between:
  • firefox
  • ie
  • netscape
  • chrome
  • <empty>

Default value is: firefox


These values can be changed while creating the campaign session from XStudio.


Note about file path parameters:

Any parameter referring to a file or folder path (for instance Test root path) can be provided either using \ separator (if the tests are going to be executed on a Windows agent) or / separator (if the tests are going to be executed on a linux or MacOSX agent).

On windows, if you provide a path containing a, OS-localizable folder such as C:\Program Files, always prefer the English version (i.e. NOT C:\Programmes if you're using a french-localized Windows) or the corresponding native environment variable (i.e. %PROGRAMFILES%).




Process

  • Each test in XStudio must have his dedicated model in TestOptimal. The name of the model MUST be equal to the name of the test.

  • Each test case in XStudio must have his dedicated mCase in TestOptimal. The name of the mCase MUST be equal to the name of the test case.

  • The test cases are executed by the launcher using these REST calls:

    "<testOptimalServerUrl>/MbtSvr/app=websvc&action=exec&userid=<userName>&password=<password>&mbtFile=<testName>&mCase=<testcaseName>&browser=<browser>&mbtMode=<sequencer>&async=false"

  • The call returns the whole stats of the model execution.





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