Create qTest TestEvents

You can integrate Tricentis Tosca and qTest. This allows you to manage your test objectives and releases in qTest, with the results from your automated tests in Tosca.

To do so, you need to create qTest TestEvents in Tosca. This links 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.

This tells you exactly how your system under test is doing, in any testing phase. And how release ready it really is.

Prerequisites

To create a qTest TestEvent, you must meet the following requirements:

• You have set up the qTosca integration.

• You have ExecutionLists with automated TestCases in Tricentis Tosca.

• If you want to link to Releases and/or Test Cycles: you have Releases and/or Test Cycles in qTest.

Create a qTest TestEvent

To create a qTest TestEvent in Tricentis Tosca and link your automated tests to qTest, follow the steps below:

1. In Tricentis Tosca, select the ExecutionList(s) that you want to add to your new qTest TestEvent.

2. Right-click and select Create TestEvent for qTest from the context menu.

3. In the Connection Details section of the Create TestEvent for qTest dialog, sign in to qTest. You only have to do this once; Tricentis Tosca remembers your credentials.

   Choose from the following options:

   • Login with qTest account

     Enter the qTest API endpoint into the qTest URL field: <url of your qTest instance>/api/v3

     Then enter your qTest user name and password.

   • Login with SSO account

     Enter the qTest API endpoint into the qTest URL field: <url of your qTest instance>/api/v3

     Then enter your qTest bearer token into the SSO token field.

     To get your qTest bearer token, open qTest and click Download qTest Resources. From the API & SDK section, copy the alphanumeric bearer token without the word Bearer.

4. Click Save and connect.

5. Define where Tricentis Tosca creates the linked objects in qTest. To do so, select a specific Release and/or Test Cycle in the Select location in qTest (optional) tree. If you don't make a selection, Tosca creates the objects directly underneath the project node of the Test Execution tab in qTest.

   You can only link to Test Cycles that you created inqTest.

   When you create a qTest TestEvent in Tricentis Tosca, Toscaautomatically creates a Test Cycle for this TestEvent in qTest. You cannot link to this kind of Test Cycle.

6. In the TestEvent name (optional) field, define a unique name for your qTest TestEvent. Tosca uses the same name for the folder that contains the TestMandates of this qTest TestEvent.

   If you don't specify a name, Tosca auto-names the qTest TestEvent and its corresponding folder: qTestEvent. Additional qTest TestEvents/folders have _<number> at the end of their name, for example qTestEvent_3.

7. Click Link.

8. The subsequent dialog asks you to link the TestCases in your qTest TestEvent to qTest. To do so, perform the following actions:

   • Click OK. This opens the Link with qTest dialog.

   • In the Link with qTest dialog, select the qTest project and Module where you want your TestCases. Click Link.

9. In the confirmation dialog, click OK. This creates all necessary objects in Tosca.

10. To transfer the information to qTest and create all necessary objects , click Checkin All.

By default, Tosca tries to connect to qTest and transfer information for a maximum of 70 seconds. If Tosca is not successful within that window, it aborts. You can define a different time frame under Project->Options->QTestIntegrationAddin->Maximum time allowed for linking attempts (in seconds).

Which objects does Tricentis Tosca create?

When you create a qTest TestEvent, Tricentis Tosca creates multiple objects in Tosca and in qTest.

Tosca objects

When you create a qTest TestEvent, Tricentis Tosca creates the following objects in Tosca:

Where?	Which objects does Tosca create?
In the ExecutionLists folder	A folder with the name Linked to qTest. Tosca creates this folder only once. Within this folder, a folder with the name of the qTest Release that you linked the qTest TestEvent to. Within this folder, another folder with name of the qTest TestEvent. Within this folder, Tosca creates a TestMandate for every ExecutionList that you selected when you created the qTest TestEvent. Each TestMandate has a separate entry for every ExecutionEntry in the ExecutionList. If you create additional qTest TestEvents for the same qTest Release, Tosca adds the qTest TestEvent folders to the existing Release folder. If you create additional qTest TestEvents for another qTest Release, Tosca adds another Release folder to the Linked to qTest folder.
In the TestEvents folder	A qTest TestEvent with the name you specified when you created the qTest TestEvent. Within this qTest TestEvent, Tosca adds the TestMandates it created. If you didn't specify a name for your qTest TestEvent, Tosca auto-names it: qTestEvent. Additional qTest TestEvents have _<number> at the end of their name, for example qTestEvent_2. You can rename the qTest TestEvent: Before you checkin for the first time after creating the qTest TestEvent. After you have checked in. In this case, you need to update the link to transfer the name change to qTest. Note: if you rename a qTest TestEvent, Tricentis recommends that you also rename the corresponding folder within the ExecutionLists folder. This keeps naming consistent and avoids confusion later on (see "Change qTest TestEvents").

The screenshot below shows all Tosca objects that Tricentis Tosca creates when you create a qTest TestEvent.

Note: if you didn't specify a qTest Release to link to, you won't have the parent folder for all TestMandates of a particular qTest Release.

qTest objects

When you create a qTest TestEvent, Tricentis Tosca creates the following objects in qTest:

Where?	Which objects does Tosca create?
In the Test Execution tab	A Test Cycle for the qTest TestEvent. Within this Test Cycle, further Test Cycles: one for each ExecutionList in your TestEvent. Test Cycles in the Q4 Release in the Test Execution tab Within these Test Cycles, a Test Run for every ExecutionEntry.
In the Test Design tab	A qTest test case for every Tosca TestCase that's referenced in your ExecutionList.

Design your qTest TestEvent

Tosca Distribution Agents (DEX Agents) need access to all applications and files that you want to test. Does that mean that all DEX Agents need to have access to all applications and files?

No. This is where configurations come in. Configurations are like tags.

You create a configuration for every application that's relevant to your tests. For instance, if you test SAP but not all DEX Agents have SAP installed, create an SAP configuration. Then apply this configuration to all DEX Agents that have SAP installed.

Additionally, you assign the SAP configuration to all TestEvents that contain SAP tests. At run-time, Tricentis Tosca forwards these TestEvents only to DEX Agents with matching configurations.

• Learn how to create configurations and apply them to DEX Agents.

• Learn how to assign configurations to your TestEvent.

View qTest TestEvents in qTest

You can open qTest TestEvents in qTest directly out of Tosca.

To do so, right-click qTest TestEvent in Tosca and select View in qTest from the context menu. This opens qTest in your default browser and jumps right to the object in qTest.

Change or delete qTest TestEvents

Testing needs can change. Over time, you may want to add additional tests to drill down to specific areas of your system under test. Or remove tests you no longer need.

You can always change your qTest TestEvents, so they contain the latest and best state of your tests.

If you no longer need a particular qTest TestEvent, you can also unlink and delete it.

Migrate existing Tosca TestEvents

The main difference between qTest TestEvents and "regular" TestEvents is that qTest TestEvents contain TestMandates, not ExecutionLists. Tricentis Tosca automatically creates and adds these TestMandates when you create a new qTest TestEvent.

So what do you do if you already organized your automated tests in "regular" TestEvents, which contain ExecutionLists? And you want the same tests in your qTest TestEvents?

Tricentis Tosca offers a quick way to create a qTest TestEvent out of a regular TestEvent. You don't need to go through all ExecutionLists again and create your qTest TestEvents from scratch.

To create a qTest TestEvent out of a regular TestEvent, follow the steps below:

1. Right-click the existing TestEvent and click on Search in the mini toolbar.

2. In the subsequent Search window, go to the TQL tab.

3. Run the following TQL query: =>SUBPARTS:TestEventExecutionListLink->ExecutedBy

4. The query result lists all ExecutionLists in the existing TestEvent. Select them, right-click, and select Create TestEvent for qTest from the context menu.

5. This opens the Create TestEvent for qTest dialog. Create a new qTest TestEvent out of the ExecutionLists.

What's next

Time to check how ready your system under test really is! For information on how to run your tests, see chapter "Run your qTosca tests".