Tosca and qTest integration

You can integrate Tricentis Tosca and qTest, which allows you to combine the best of both worlds:

• qTest's Application Lifecycle Management integration and release planning.

• Tricentis Tosca's automation capabilities.

An integration lets you manage your test objectives and releases in qTest, with the results from your automated tests in Tosca. This tells you exactly how your system under test is doing, in any testing phase. And how release ready your system under test really is.

Compatibility

Tosca 16.0 is compatible with qTest SaaS or OnPremises 11.3 or later.

Set up the integration

To set up the integration between Tricentis Tosca and qTest, perform the following actions:

• Make sure that you meet all prerequisites.

• Create the integration infrastructure.

Prerequisites

On the Tosca side, make sure to meet the following requirements:

• You have installed Tricentis Tosca.

• You have installed Tosca Server, including the server features Tricentis Tosca Administration Console, Tosca Distributed Execution, and REST API Service.

• You have set up and enabled Tricentis Notification Service.

• You have set up Tosca Distributed Execution, either with or without AOS.

On the qTest side, make sure to meet the following requirements:

• You have the qTest user permissions listed in the qTest documentation (see "Prerequisites").

• If you want to trigger executions out of qTest: you are an Elite qTest user. Only Elite users have access to qTest Launch, where you trigger executions.

Create the integration infrastructure

To set up the necessary infrastructure, follow the steps below:

1. Create an extra workspace for qTest. qTest uses this workspace to connect to Tosca for updates and triggering test executions.

   Do not treat this workspace as a regular "working" workspace for users. It serves as a background workspace for qTest.

   Two important things to consider:  If you use Tosca Server with HTTPS, this workspace must be a Tosca Server Repository workspace. The workspace must always be closed. If you link or trigger an execution out of qTest and the workspace isn't closed, qTest cannot perform the task.

2. If you're using qTest SaaS, ensure that the machine that holds the Tosca Distribution Server accepts requests from the qTest client.

   • For inbound requests, you may have to whitelist the qTest AWS IP addresses.

   • For outbound requests, whitelist the qTest domain URL *.qtestnet.com.

3. Go to your qTest project and activate the Automation Settings as described in the qTest documentation. Enter the workspace URL of the qTest workspace that you created in step 3.

What's next

Now that you have set up the Tosca-qTest integration, it's time to bring your automated tests to qTest. To do so, create qTest TestEvents. qTest TestEvents link your automated Tosca tests to your qTest Releases. It doesn't matter where you trigger these tests; you see results in Tosca and in qTest.

Alternatively, link TestCases to qTest to track Tosca automation progress in qTest.