Launch 1.5.8 Release Notes

Tosca and qTest Integration Improvements

Run Tosca Test Cases within qTest Launch

There are some Tosca Test Cases that need to be associated with qTest Manager.

1. Navigate to qTest Launch

2. Schedule Run on selected Tosca Test Cases

3. Wait for the schedule to be completed and the test result is submitted to qTest

4. Each Test Run with its Test Steps should be submitted to qTest Manager. Test Runs and Test Steps should have statuses different than Unexecuted (Other steps after any skipped Test Step are not logged and are not submitted to qTest)

Tosca Distributed Execution with Automation Object Service

Tosca 13.0 introduced Distributed Execution with Automation Object Service (AOS). For more information, go to https://documentation.tricentis.com/tosca/1300/en/content/distributed_execution/wsle_advantages.htm.

Security Enhancements

• Fixed security issue as reported by NodeJS community: https://nodejs.org/en/blog/vulnerability/february-2020-security-releases/

 

Bug Fixes

Ticket #	Component	Description
36931	Parser	The JUnit for Java parser won't parse the result properly if the result contains <testsuites> (plural) tag. This has been fixed.
NA	Tosca Integration	When updating Test Step information in Tosca, the changes are not reflected in qTest Manager. The Test Case Version remains the same and the updated steps show as "UNEXECUTED". The release of Automation Host 2.3.3 fixed the issue.