Gradle Launcher (gradle.jar)

The Gradle launcher allows interfacing with Gradle.



Configuration

The gradle.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
Gradle
Gradle install path This must indicate the path to the Gradle bin directory.

Default value is: /usr/local/bin
Optional arguments This can contain optional arguments for Gradle.

Default value is: -Penv=qa
Test Suite This must indicate the name of the Gradle testsuite.
Default value is: fasttests
Console redirection file path This must indicate the path where the traces will be redirected.

Default value is: /tmp/console.txt
Output file format This must indicate the format of the results file.
The format can be nose or TestNG and it depends on how you wrote your tests.

Default value is: nose
Output file path This must indicate the path to the results file.

Default value is: /tmp/nosetests.xml


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


Process

The tests are executed by the launcher using this syntax:


"<gradleInstallPath>/gradle" "<optionalArguments>" <testSuite>


And this is executed from the working directory <gradleInstallPath>


Then, the launcher will search if there is a corresponding entry for each test case in the generated results file. This parsing will differ depending on the generated format.



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