Integrate Cerberus with XQual - Launcher

Cerberus Launcher (Cerberus.jar)

XQual integrates natively with Cerberus — centralize your Cerberus test executions, results, and reports from a single dashboard.
Why QA teams use XQual with Cerberus
  • Centralize Cerberus results alongside 100+ other frameworks in a single dashboard
  • Link test cases to requirements and defects for full traceability
  • Launch, monitor and report across all your frameworks simultaneously
→ Start your free XQual trial

Configuration

The cerberus.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
REST Connection
Base URL This must indicate the base URL of your Cerberus's REST API.
This URL MUST not include an ending slash.

Default value is: https://acme.cerberus-testing.com
API Key This must indicate the authentication key to connect to the REST API.

Default value is: <empty>
Configuration
Country This must indicate the country where will be executed the tests.

Default value is: FR
Environment This must indicate the country environment will be executed the tests.

Default value is: PROD
Robot This must indicate the robot name.

Default value is: CerberusChrome

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

Process

The tests are executed by the launcher by some calls to the REST API:

  • When the session is started a connection is established with the REST API.
  • For each test in the campaign, all the testcases are queued to be executed by Cerberus (using the addToExecutionQueue method).
  • Then the launcher waits for all the testcases to be executed (using the resultCI method).
  • All the details are fetched (using the getTagDetails method).
  • The details then parsed to retrieve the results and a few other information of each testcase and all the data are stored in XQual.

Mapping

  • In XQual you need to create a testcase for each Cerberus testcase
  • Testcase names must be unique
  • Test or ancestor folder names are not used

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 XQual (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

Next steps with XQual