Odin Technology® Axe Launcher (odin_axe.jar)

The Odin Technology® Axe launcher allows interfacing with Odin Axe 3.5 compiled scripts. This allows the transportation of the executable scripts and does not require an Axe license to execute but does require an Axe project structure of at least config / results / scripts to be present.


The odin_axe.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
Axe Config
Default Axe Run config file This is the run config used by Axe (the same as you would use in Axe IDE). Add in your own config files.

Default value is: Selenium_Firefox
Input Results Only Set this to true if you only want to input the results generated by Axe tool

Default value is: false
Axe Project
Axe install path This must indicate the Axe install path.

Default value is: C:/Program Files (x86)/Odin technology/Axe
Project Name This must indicate the project name

Default value is: MyProject
Project Path This must indicate the project path

Default value is: C:/MyProject
Config Path This must indicate the config path

Default value is: /config
Results Path This must indicate the results path

Default value is: /results
Scripts Path This must indicate the scripts path

Default value is: /scripts
Selenium Settings
Selenium Web Driver If you are running with the Selenium Web dirver then set this boolean to true.

Default value is: false
Java Path This must indicate the Java path.

Default value is: C:/Program Files (x86)/Java/jre7/bin
Server options This must indicate the options to pass to the server.

Default value is: -trustAllSSLCertificates
Server Jar PAth This must indicate the path of the server jar.

Default value is: C:/Selenium/selenium-server-standalone-2.39.0.jar

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%).


The tests are executed by the launcher using this syntax:
<Axe Project Path>/<scripts path>/<Axe suite name>/<XStudio test name>.exe

Note - The Axe suite name has to match the SUT name being used in the Campaign Session.

Test should be setup in XStudio as they appear in Axe IDE, as separate Tests and NOT as Test Cases.

The test will be marked as passed or failed depending on the results file generated by Axe. The Axe results xml file is parsed by the launcher. The Axe results xml file is also attached to the testcase execution in XStudio.

If running Selenium RC then the launcher will start Selenium automatically from port 4444 and will increment the port number if the server is already in use.


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


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