Update qTest links

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.

You can update existing links if you, for instance, change a qTest TestEvent.

Updating is important. Tricentis Tosca and qTest don't synchronize automatically. If you make changes to your Tosca tests, you need to update them in qTest.

When you can update

You can update once links are live in qTest. Links go live once you go through the linking process in Tosca and checkin.

How often you can update

You can update as often as you want, but you can only have one link per object. Whenever you update a link, Tricentis Tosca overwrites the old information.

Update in qTest

If you have made changes to your tests in Tosca, you need to update them in qTest. To do so, follow the steps below:

  1. In Tricentis Tosca, select the object(s) that you want to update.

    Note that you can only multi-select objects of the same type. For instance, you can select multiple TestCases at once, but not a TestCase and a TestCase folder.

  2. Right-click and select Update in qTest from the context menu.

  3. If you're no longer signed in, enter your qTest credentials into the Connection Details section of the Update in qTest dialog as described here.

  4. Click Save and connect.

  5. Optionally, select a new location for your linked objects in qTest:

    • Select a different qTest project from the Select qTest Project drop-down menu.

    • For TestCases, you can also define a different qTest Module in the Select qTest Module section.

  6. If you're updating TestCases and you don't want to change the Module, confirm by selecting the qTest Module the TestCase is currently linked to.

  1. Click Link.

  2. In the confirmation dialog, click OK. This saves the information in Tosca.

  3. To transfer the updated information to qTest, 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).

Reuse qTest TestEvents in other Test Cycles or Releases

You've done it all: you created your qTest TestEvents, which are linked to Test Cycles and Releases in qTest. You've run your tests, and your system under test behaved as expected. Then your system under test changed, and now it's time for a new test and release cycle.

If you want to run the same tests in the new test and release cycle, you need to create new qTest TestEvents out of the existing qTest TestEvents.

To do so, follow the steps below:

  1. Right-click the existing qTest 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->UsedOwnedItems:ExecutionList

  4. The query result lists all ExecutionLists in the existing qTest 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, linking it to the new Test Cycle/Release.

Do not copy & paste or cut & paste objects, neither in Tosca nor in qTest. Copy & pasting breaks important links between Tosca and qTest; cut & pasting causes issues with results reporting.

What's next

Run your updated qTest TestEvent to see how release-ready your system under test really is.