Manager 9.9.4 Release Notes

February 19, 2020

qTest and Tosca integration enhancements

Test Cases

Previously, Test Cases created in qTest were not marked as Tosca Test Cases, when created via these methods:

1. When qTest tests get created via the Jenkins integration option.

2. When qTest tests get created via the Universal Agent / Automation Host option.

3. When tests are converted from Tosca > qTest.

4. When qTest test get created via the create test case API.

The following APIs are enhanced to handle the optional values for a Tosca Test Case GUID and a Tosca Test Case Node Path:

• https://qtest.dev.tricentis.com/#/test-log/submitAutomationLog

• https://qtest.dev.tricentis.com/#/test-log/submitAutomationLog

• https://qtest.dev.tricentis.com/#/test-log/submitAutomationLog

• https://qtest.dev.tricentis.com/#/test-case/createTestCase

• In qTest, if you delete a Tosca Test Case directly, or via the parent module, the link between the Tosca and qTest Test Case is removed within qTest Manager.

• In qTest, if you restore a Tosca Test Case directly, or via the parent module, the restored Test Case becomes an orphaned Tosca Test Case in qTest Manager with no link between its qTest ID and the Tosca Test Case GUID.

Modules

The Create a Module API provides 2 new properties to submit the optional values of a Tosca Folder GUID and Tosca Folder Node Path:

• https://qtest.dev.tricentis.com/#/module/createModule

• In qTest, if you delete a Tosca Module directly, or via the parent module, the link between the Tosca and qTest Module is removed within qTest Manager.

• In qTest, if you restore a Tosca Module directly, or via the parent module, then the restored Module becomes a qTest native Module with no link to the Tosca Folder GUID.