Tosca qTest integration

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

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

• Tricentis Tosca's automation capabilities.

When to use what

Tricentis Tosca is your on-premise automation platform. Here is where you design automated tests and create all necessary links between Tricentis Tosca and qTest.

qTest is available on premise or as a cloud-based product. In qTest, plan your releases and link them to requirements, i.e. your test objectives. You can use the requirements that you specified in your ALM tools, for instance Jira. For more information on working with qTest, see the qTest documentation.

Prerequisites

To integrate Tricentis Tosca and qTest, you must meet the following requirements:

• You have installed Tricentis Tosca and the Tricentis Tosca Server.

• You have installed qTest OnDemand or OnPremise 10.2 or later.

• You are an Elite qTest user. Only Elite users have access to qTest Launch, which you need to run your tests.

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

Basic workflow

To integrate Tricentis Tosca and qTest, perform the following actions:

• Set up the integration infrastructure.

• Create the necessary links and run your tests.

Set up the integration infrastructure

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

1. Set up your work environment in Tosca Commander. To do so, create multi-user workspaces as described in chapter "Create multi-user workspaces".

2. Set up Tosca Distributed Execution. Choose one of the following setup options:

   • "Set up Tosca Distributed Execution with AOS"

   • "Set up Tosca Distributed Execution with AOS | HTTPS"

   • "Set up Tosca Distributed Execution without AOS"

   • "Set up Tosca Distributed Execution without AOS | HTTPS"

3. 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.

   This 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.

4. If you are using qTest OnDemand, ensure that the machine that holds the Tosca Distribution Server accepts requests from the qTest client. You may have to whitelist the qTest AWS IP addresses.

5. 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.

Create the necessary links and run your tests

To use the integration, follow the steps below:

1. In qTest, set up your basic release structure:

   • Create a Test Plan with releases and builds.

   • Create or import your requirements.

2. In Tricentis Tosca, design your automated TestCases:

   • Scan your application to create Modules.

   • Create TestSteps from these Modules.

     You can also create your TestSteps from the Modules of the Standard subset.

   • Steer your application (see chapter "Steer with Engines 3.0" and chapter "Steer with Classic Engines").

3. Link your automated tests with qTest.

   Linking your tests creates the necessary objects in qTest. You can always update or remove links.

   If you already have a working qTest project with existing test cases, you can also link these test cases with Tosca. See the qTest documentation for information on how to do so, compatible versions, and requirements.

4. In qTest, schedule or trigger your execution.

5. View your results in qTest.

What's next

Check out chapter "Link with qTest" for information on linking Tosca tests with qTest.