Launchers / Automated tests

MrSuricate Launcher (mrsuricate.jar)

The MrSuricate launcher allows interfacing with MrSuricate execution plateform.

Configuration

The mrsuricate.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
Mr Suricate
Mr Suricate URL This must indicate the URL of MrSuricate server

Default value is: https://api.mrsuricate.com/api-v2
Email This must indicate your account's email address.

Default value is: my_email@acme.com
Password This must indicate your account's password.

Default value is: my_password
Customer Id This must indicate your account's customer ID.

Default value is: 123
Browser This must indicate on which browser to run the tests.

Valid values are: Chrome, Firefox, Safari, Edge
Default value is: Chrome

These values can be changed while creating the campaign session from XQual.
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%).


Process

The tests are executed by the launcher using this syntax:

When the session starts (initialize())

Authenticate to MrSuricate

api-v2/auth/login

Fetch all the scenarios available

api-v2/customers/XXX/scenarios/get

Map the scenarios available with the tests that are going to be executed in this session


Run a schedule containing all the scenarios corresponding to the tests included in this session

api-v2/customers/XXX/runs/schedule

Map the run ids with the scheduled scenarios


For each test executed (run())

retrieve its corresponding run id


Check the status of the execution every 2 second (max 1 hour) until the run id is "Completed"

api-v2/customers/XXX/runs/<run-id>/get



The test will be marked as passed or failed depending on the json report returned by MrSuricate.