Mocha Launcher (mocha.jar)

The Mocha launcher allows interfacing with Mocha (also called MochaJs) (.js) scripts.

Configuration

The mocha.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
General
Test root path	This must indicate where are located all the .js scripts. This is a root path. Each test in XStudio has a canonical path that will be appended to this path. This path MUST not include an ending slash. Default value is: `D:/Tests/mocha`
Test level	You can define at which level you make the association in between Mocha and XStudio. 2 options are available: Test: each Mocha file (.js) will be corresponding to a test in XStudio Test case: each Mocha file (.js) will be corresponding to a test case in XStudio Test and test cases: each Mocha file (.js) will be corresponding to a test in XStudio. Then the launcher will parse all the individual "test" item returned by the reporter and will try to map their results to XStudio's test cases. Default value is: `Test and test cases`
Mocha
Mocha install path	This must indicate where is installed Mocha on the host. The Mocha runner (`mocha.exe`) must be present in this folder. Default value is: `C:/Program Files/mocha`
Reporter	This must indicate the reporter used to parse the result. 2 reporters are currently available: mocha-json-file-reporter: a reporter that generate a JSON file on disk JSON: a reporter that generates a JSON trace Others could be added on demand. Default value is: `mocha-json-file-reporter`
Mocha options	This may include some optionnal arguments you want to pass to the Mocha test runner. Default value is: `<empty>`

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

Prerequisites

You'll need to have NodeJs installed then install Mocha and the Mocha JSON File Reporter.

Install Mocha

npm install -g mocha

Install the Mocha JSON File Reporter

If you pick the mocha-json-file-reporter reporter in your configuration, you need to install it first:
npm install -g mocha-json-file-reporter

Process

If you are using a configuration with Test level "Test and test cases"

Each test in XStudio must have his dedicated .js script. The name of the script (without its .js extension) MUST be equal to the name of the test.
The mocha test runner is launched by the launcher using this syntax:
_mocha.cmd -R "<reporter>" <options> "<testRootPath>/<testPath>/<testName>.js"
and from the working directory "<mochaInstallPath>"
The file <testRootPath>/reporter.json or the console trace (if you chose the JSON reporter) is parsed to retrieve the results of each test case

If you are using a configuration with Test level "Test"

Each test in XStudio must have his dedicated .js script. The name of the script (without its .js extension) MUST be equal to the name of the test.
The mocha test runner is launched by the launcher using this syntax:
_mocha.cmd -R "<reporter>" <options> "<testRootPath>/<testPath>/<testName>.js"
and from the working directory "<mochaInstallPath>"
The file <testRootPath>/reporter.json or the console trace (if you chose the JSON reporter) is parsed and all the results are stored as the default unique test case's steps

If you are using a configuration with Test level "Test case"

Each test case in XStudio must have his dedicated .js script. The name of the script (without its .js extension) MUST be equal to the name of the test case.
The mocha test runner is launched by the launcher using this syntax:
_mocha.cmd -R "<reporter>" <options> "<testRootPath>/<testPath>/<testName>/<testcaseName>.js"
and from the working directory "<mochaInstallPath>"
The file <testRootPath>/reporter.json or the console trace (if you chose the JSON reporter) is parsed and all the results are stored as the test case's steps

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

Launchers / Automated tests