- Introduction
- Manual testing
- Autoit
- Ant
- Agilitest
- Bat
- Bat With Params
- Beanshell
- Cerberus
- Cucumber
- Cucumber v2 (BDD & Gherkin support)
- Cypress
- eTASQ Motion (Ponant)
- Executable
- FitNesse
- Gatling
- Generic Version-Control
- Git, Gitlab, Github
- Gradle
- Java
- Jar
- JMeter
- JMeter SQL
- JMeter Web
- JUnit
- Katalon
- Katalon v2
- Lynqa
- Marathon
- Maven
- Mocha
- Mr Suricate
- NeoLoad
- NUnit
- Odin Axe
- Odin Axe Results
- Offline
- Perl
- PHPUnit
- Playwright
- Postman (Newman)
- Protractor
- Python
- PyUnit
- PyTest
- QF-Test
- Quick Test Pro/UFT
- Ranorex
- Rapise
- ReadyAPI
- RobotFramework
- RobotFramework v2
- RobotFramework v3
- RobotFramework v4
- Sahi
- Sahi 3.5
- Sahi 4.0
- Sahi 6.0
- Selenese
- Selenium HTML
- Selenium 3
- Selenium Java
- Selenium .NET
- Selenium Python
- Shell
- Sikuli
- SikuliX
- SilkTest
- SoapUI
- SoapUI Load
- SoapUI Security
- SOATest
- SQL Compare
- SQL Select
- Squish
- SVN (Subversion)
- Tape
- Tcl
- TestComplete
- TestComplete v2
- TestExecute
- TestExecute v2
- Testim
- TestNG
- TestOptimal
- TestOptimal Simple
- TestPartner
- TestStand
- VisualStudio
- VisualStudio Coded UI
- WAPT
- WebdriverIO
- WebUI
- XCI
- xUnit.net
- Success (skeleton)
- Random (skeleton)
- Proxy
Lynqa Launcher (lynqa.jar)
The Lynqa launcher allows interfacing with Lynqa execution plateform.Configuration
Thelynqa.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 URL of Lynqa service Default value is: https://my_lynqa_server
|
| API Key | This must indicate the API Key to authenticate to the server. Default value is: aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee
|
| Target | |
| Base URL | This must indicate the URL of the target app Default value is: https://my_target_app
|
These values can be changed while creating the campaign session from XQual.
Process
The tests are executed by the launcher using this process:Generate the input JSON for Lynqa
A JSON document containing the testcase procedure is built in Lynqa format
Call Lynqa service to execute the testcase
The method testRuns (POST query) is called with the JSON document in the body of the query
A runId is returned.
Wait Lynqa service to report the end of execution
The method getStatus (GET query) is called with the runId as parameter every second until a status success, failed or terminated is returned
The output is parsed and converted to structured messages that are visible in XQual.
In case of a success, all screenshots referenced by Lynqa are downloaded and embedded in the messages as well.
A timeout of 1 hour is also applied. If the timeout expires, the launcher ignores the execution and returns an error to XQual.
testRuns (POST query) is called with the JSON document in the body of the queryA
runId is returned.