qTest and Tosca Integration: Quick Start Guide

You can use qTest's built-in integration with Tricentis Tosca to combine qTest's Application Lifecycle Management (ALM) and release planning with Tricentis Tosca's automation capabilities.

This quick start guide describes the integration steps you need to perform in qTest. Some steps require prior action in Tricentis Tosca. For a complete overview of how to set up the qTest and Tosca integration, refer to the Tricentis Tosca manual.

Prerequisites

We offer two different authentication methods for qTest and Tosca integration: client ID-secret or username-password. These options share most prerequisites, though there are some key differences in version compatibility and workspace requirements.

As of Tosca 15.2, you can determine which authentication method you need to use based on the following requirements.

Note that we recommend that you use an HTTPS connection to connect to Tosca to ensure you are as secure as possible.

When to use client ID-secret authentication:

  • If you use a server repository workspace

  • If you have an HTTPS connection

When to use username-password authentication:

  • If you use any other workspace type that is not a server repository workspace

  • If you have an HTTP connection

qTest does not automatically determine which authentication method to use. After you determine your needs, use the configuration option that works best for your setup.

Universal prerequisites

You must meet the following prerequisites for any type of setup:

  • You are an Elite qTest user.

  • You have the following permissions in the qTest Project that is integrated with Tosca: Create Modules, Edit Modules, Edit Test Case Assignment, Create Test Cases, View Test Cases, Update Test Cases, Delete Test Cases, Create Test Cycles, Update Test Cycles, Delete Test Cycles, Create Test Runs, and Delete Test Runs.

  • You have configured a multi-user environment in Tosca and use Tosca Distributed Execution (DEX).

  • To integrate qTest SaaS, the corresponding Tosca server must be reachable on the internet and requires a public DNS.

    SaaS customers can add a custom header for outbound requests between qTest and Tosca, allowing them to place a proxy in front of their Tosca server. For more information about adding a custom header, refer to qTest and Tosca Integration: Quick Start Guide.

Additional prerequisites for username-password authentication

You can use the username and password method authenticate HTTP connections in all versions, as HTTP connections do not require authorization in Tosca. This authentication method also works for HTTPS connections in Tosca 15.1 or lower.

You must meet the following requirements to integrate Tricentis Tosca and qTest for HTTP or HTTPS connections that use a username and password authentication method:

  • You use qTest version SaaS or 2024.1 OnPremises.

  • For HTTP connections, you have installed Tricentis Tosca and a Tricentis Tosca Server version 15.1 or higher.

  • For HTTPS connections, you have installed Tricentis Tosca and a Tricentis Tosa Server version from 15.1 to Tosca 15.1 .

Additional prerequisites for client ID-secret authentication

System administrators can use the client ID and secret method for both HTTP and HTTPS connections to control which users and applications have permission to connect to the DEX server. This authorization ensures the DEX environment is secure. To upgrade to Tosca 15.2 or later, you are required to use the client ID and secret method to authenticate HTTPS connections.

You must meet the following requirements to integrate Tricentis Tosca and qTest for HTTP or HTTPS connections that use clientID and secret authentication method:

  • You use SaaS or qTest 11.3 On Premise or later.

  • You have installed Tricentis Tosca and a Tricentis Tosca Server version 15.2 or higher.

  • You have generated client ID and secret keys.

  • You have set up a Tricentis Server Repository workspace.

qTest workflow

Use the instructions below to complete the integration steps you need to perform in qTest. To see a full overview on how to integrate Tosca to qTest, refer to the Tricentis Tosca documentation.

If you need additional information on how to integrate Test Cases from qTest to Tosca, refer to Integrate from qTest to Tosca.

Configure Tosca integration settings

To set up Tosca integration, follow these steps:

  1. In qTest Manager, select the Gear icon and go to Automation Settings.

    The Automation Settings screen appears.

  2. In the Automation Integration section, turn on the Activation status.

  3. In the mapping table, map the following Tosca statuses to qTest: Passed, Failed, Error, and Canceled. Map these statuses to successfully submit test results from Tosca to qTest.

  4. In the Tosca Integration section, click the Activation status button to toggle the activation on.

  5. In the Protocol field, select HTTP or HTTPS, depending on the protocol you are using for your workspaces.

  6. Enter the Hostname of your Tosca server. For example, localhost:6060.

  7. After you connect to the host, select Load Workspaces to populate all available workspaces on the Tosca server.

  8. From the Workspace dropdown, select the qTest integration workspace you set up in Tosca. For more information about the qTest integration workspace set up in Tosca, refer to the Tricentis Tosca documentation.

  9. Select your authentication mode: Username-Password or ClientID-Secret.

    • If you selected Username-Password, enter the Username and Password for authentication.

    • If you selected ClientID-Secret, enter the Client and Secret for authentication.

  10. Enter the Monitoring Service URL. This field is only required if you are using a Tosca version older than 15.0.

    For information on locating the Monitor Service URL, refer to Locate the Monitor Service URL

  11. Select how often you want to pull data from the workspace in the Update Workspace Timeout field.

  12. Select Save. A message confirms Tosca integration is enabled.

  13. Click Refresh to refresh your browser and apply the changes.

Launch your tests in qTest

For information about launching tests in qTest, refer to Schedule Test Execution for Tosca TestEvent from qTest.

Known Limitation: The Tosca workspace must be closed before tests can be executed from qTest.

View the results

You can view test results in either qTest or in Tosca.

To learn how to view results in qTest, refer to View your Tosca Execution Results in qTest.

To learn how to view results in Tosca, refer to the Tricentis Tosca documentation.

Access linked Tosca objects in Tosca

You can access linked Tosca objects directly from qTest. To view a linked object in Tosca, click Open in Tosca Commander on the object screen.