Jenkins Plug-in Release Notes
Jenkins Plug-in 1.4.6 Release Notes
July 17, 2020
|None||Jackson Library||Fixed vulnerabilities|
Jenkins Plug-in 1.4.5 Release Notes
February 10, 2020
Previously, when executing Tosca tests with Jenkins plug-in, only FAILED test logs are submitted to qTest Manager. Now, the test logs for PASSED test cases are also submitted to qTest Manager.
When executing Tosca test with qTest Jenkins Plug-in, the updated Tosca Test Steps, which are generated in the XML result, will also be updated to the test run in qTest Manager.
|None||Jenkins Plug-in||Fixed vulnerabilities|
Jenkins Plug-in 1.4.4 Release Notes
August 09, 2019
|30380||Jenkins Plug-in||Jenkins Plug-in doesn't show builds higher than 39999|
Jenkins Plug-in 1.4.2 Release Notes
June 24, 2019
|24641||Jenkins Plug-in||qTest Jenkins Plug-in cannot bypass proxy even the proxy is configured in No Proxy Host in Jenkins proxy setting|
|22269||Jenkins Plug-in||qTest Jenkins Plug-in creates test suite with an incomplete name|
Jenkins Plug-in 1.4 Release Notes
August 24, 2018
We added the ability to execute Tricentis Tosca tests and the results will submit to qTest Manager. This feature can be achieved via FreeStyle project configuration or Pipeline script generation. Refer to Jenkins and Bamboo Integration to configure Tosca integration in qTest Jenkins Plug-in.
Jenkins Plug-in 1.3.1 Release Notes
April 6, 2018
|15799, 15994, 15949, 15773, 15906||Jenkins Plug-in||Update qTest Jenkins Plug-ins to work with Jenkins 2.113.|
|15082||Jenkins Plug-in||Fixed an issue with Proxy configuration in Jenkins.|
|15243||Jenkins Plug-in||Unable to retrieve data from Manager in Jenkins.|
Jenkins Plug-in 1.3.0 Release Notes
March 12, 2018
New Features and Enhancements
Jenkins Plug-in 1.3.0 now supports Jenkins Pipeline with qTest Manager for advanced continuous integration scenarios. You can now generate a pipeline script from the qTest Jenkins Plug-in to submit test results to qTest Manager. The script, once generated, can be used as a step in your entire pipeline scripts.
Previously, if you were using Jenkins Pipeline you would need to use the QASymphony API directly to upload your test results.
Jenkins Plug-in 1.2.1 Release Notes
January 25, 2018
Users can install qTest Jenkins Plug-in directly from their Jenkins Plug-in Manager. If you currently have the Jenkins Plug-in installed, your plug-in version will automatically update.
Unable to maintain Test Steps and Expected result using Jenkins.
Suggestion to enhancement for automation tests to be submitting in order into qTest.
Support proxy configuration in Jenkins.
Added an option to override existing test case steps with new steps when submitting test results, namely "Overwrite existing test steps". This option is enabled (checked) by default to keep it backward compatible with previous version of qTest Jenkins Plug-in.
Used bulk upload API to upload thousands of test results to qTest Manager.
Added an ability to specify the destination that the Test Execution results go, such as a Release, Test Cycle, or Test Suite.
JUnit test result now is submitted to qTest Manager in the same order they are laid out in the junit.xml.
The following screenshot shows the enhanced UI of the qTest Jenkins Plug-in. For instruction how to get the most from the plug-in, refer to Jenkins and Bamboo Integration.
For more information, refer to Jenkins and Bamboo Integration.