This feature is available in qTest Elite and Enterprise packages. We provide a command line tool which is capable of kicking off eggPlant scripts which reside on your local machine and reporting test results in JUnit-compatible format back to qTest. Automation Test Cases and Test Runs are automatically created in qTest so you will not need to manually do it.
In order to setup the integration, please follow the steps below:
See our instructions below:
In order to receive test results submitted by eggPlant Connector, you will need to activate the Automation Integration feature in your qTest project.
In the extracted directory above, you can find the config.properties file, which stores all available configurations. You will need to modify the keys in the file as described in the table below.
|qtest.url||Yes||The URL to access your qTest instance|
|qtest.tokenstring||Yes||The token to login to your qTest instance. You can get the token from the qTest Resources page
|qtest.project.id||Yes||ID of the qTest project to which you want to report test execution results to. You can get the project ID from its URL or on the Site Administration Projects page:
When test results are submitted to qTest, Test Runs are automatically created in qTest if they do not already exist.
You can specify a qTest Test Suite where the submitted Test Runs will be located using its ID or PID.
If it is omitted, one Test Suite is created per execution date to contain the Test Runs. If eggPlant tests are executed multiple times in one day, all Test Runs are located in the same Test Suite of that day. The Test Suite is named as eggPlant yyyy-mm-dd, in which yyyy-mm-dd is the execution date, and it is located under the Test Execution tree's root.
Specify an execution date in yyyy-mm-dd which will be used in the default Test Suite name.
If it is omitted, qTest will use the test log submitted date to create the Test Suite.
When test results are submitted to qTest, Test Cases are automatically created in qTest if they do not already exist.
All eggPlant Test Cases are located under the module eggPlant Automation located under the Test Design tree's root.
If you specify a parent module using its PID or ID, the eggPlant Automation module will be created under the parent module.
|eggplant.results.directory||Yes||Directories in which test results are located. You can specify multiple directories, separated by | character. Use / in the directory paths
You can use wildcards to specify result directories as below:
You can specify an eggPlant command line to kick off eggPlant scripts before collecting the test logs.
If only collect the existing test logs and submit them to qTest, please leave this key empty
If it is Yes, each <testcase> tags in JUnit XML test logs is created as one Test Case in qTest
|submit.latest||No||If this is yes, only the latest test logs are submitted. Otherwise, all existing test logs which have not been reported to qTest will be submitted.|
|submit.automatedstepresults||No||By default the key’s value is yes
After you have completed modifying the config.properties file, you are ready to execute the tool.
java -jar eggplant-connector-1.0.0.jar
java -jar eggplant-connector-1.0.0.jar --help