Tosca and qTest integration

You can integrate Tricentis Tosca and qTest (opens in new tab), 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 2024.2 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, make sure to do the following:

• Meet all necessary setup prerequisites.

• Create the integration infrastructure.

Prerequisites

On the Tosca side, you need to meet these requirements:

• You have installed Tricentis Tosca.

• You have installed Tosca Server.

• You have set up and enabled Tricentis Notification Service.

• You have activated the integration in the qTest Integration tab of the Tricentis Service Configuration.

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

On the qTest side, you need to meet these requirements:

• You have the qTest user permissions listed in the "Prerequisites" in the qTest documentation (opens in new tab).

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

Integration infrastructure

To set up the necessary integration infrastructure, follow these steps:

1. Create an extra workspace for qTest. qTest uses this workspace to connect to Tosca for updates and test runs. Keep these important things in mind:

   • DO create a Tosca Server Repository workspace if you use Tosca Server with HTTPS.

   • DO keep the workspace closed at all times. If you link or trigger a test run out of qTest and the workspace isn't closed, qTest can't perform the task.

   • DON'T treat this workspace as a regular "working" workspace for users. It only serves as a background workspace for qTest.

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 (opens in new tab).

   • 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 (opens in new tab). Enter the workspace URL of the qTest workspace that you created in step 1.

What's next

Now that you've set up the integration, it's time to bring your automated tests to qTest: create your first qTest TestEvent.

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.