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

However, 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 modify your qTest TestEvents, so they contain the latest and best state of your tests.

Tricentis strongly recommends that you maintain your automated tests in Tricentis Tosca. Don't just rename, reorder, or delete linked objects in qTest.

The difference between qTest TestEvents and "regular" TestEvents

qTest TestEvents differ from "regular" TestEvents in one major way: qTest TestEvents contain TestMandates instead of ExecutionLists (see chapter "Which objects does Tricentis Tosca create?").

If you make changes to your ExecutionLists, you also need to update the corresponding TestMandates.

Make modifications

You can make various changes to your tests. Expand the dropdowns below to get detailed information on how to update your qTest TestEvent in Tosca:

Delete qTest TestEvents

If you don't need a qTest TestEvent anymore, you can unlink and delete it. For more information, see chapter "Remove qTest links".

What's next

When you make modifications to a qTest TestEvent in Tosca, you need to transfer the information to qTest. Click here to learn more about updating links.

Once you've done so, run your updated tests.