Odin Technology® Axe Results Launcher
(odin_axe_results.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.



Configuration

The odin_axe_results.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 Project
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
Results Path This must indicate the results path

Default value is: /results


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


Process

In this variant of the Odin Technology® Axe launcher we expect the tests have already been executed.
This launcher will just parse the results file to update XStudio with the results. The results file must be located in <resultsPath>/<sutName>/results.xml
(Note - The Axe suite name has to match the SUT name being used in the Campaign Session)




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