Run your qTosca tests

qTest TestEvents allow you to link automated Tosca tests to qTest. To check the state of your release, you need to run these tests. This lets you know how release-ready your system under test really is - and where it maybe needs a little more attention.

Choose one of the following options:

• Run all tests in your qTest TestEvents.

• Run individual tests if you want to focus on a particular aspect of your system under test.

Run all tests in your qTest TestEvents

To run all tests in your qTest TestEvents, trigger the execution in one of the following ways:

• Trigger the execution of the qTest TestEvents in Tosca.

• Schedule or trigger the execution of the corresponding Test Cycles in qTest.

It doesn't matter where you trigger the execution. Both Tosca and qTest receive the results.

• In Tosca, you see results in the qTest TestEvent, the TestMandates, and the ExecutionLists.

• In qTest, you see the results in the corresponding Test Cycles and Test Runs.

Run specific tests

You don't have to run all your tests, all the time. You can focus on specific aspects of your system under test, for example a single workflow in the user interface. To do so, trigger the execution of the TestMandates that are linked to your qTest TestEvent.

You can trigger the execution of the following objects:

• One or more TestMandates.

• One or more ExecutionEntries within the TestMandates.

• A combination of the two.

Tosca only reports results to qTest if you trigger the execution of the TestMandates. If you trigger the execution of the linked ExecutionLists, Tosca does not send results to qTest.

To trigger the execution of specific tests, follow the steps below:

1. Right-click the tests that you want to run and select Run from the context menu.

2. Tosca displays the results in the TestMandates and the linked ExecutionLists. To transfer results to the corresponding Test Cycles and Test Runs in qTest, click Checkin All.

Archive the results of your qTosca tests

You can archive old test logs to keep your workspace uncluttered and fast.

When you run qTest TestEvents via Tosca Distributed Execution, you can archive whenever you like, independently of when you check in. You can also discard the ActualLog during the archiving process - or leave it.

If you want to archive the results of your TestMandates, you need to keep the following things in mind:

• Tosca only sends the results of ActualLogs to qTest; it doesn't send archived results. The data transfer happens when you check in. So if you run a TestMandate, archive the log, and then check in, Tosca doesn't send any results to qTest. You need to check in your results before you archive the log.

• Make sure that you discard the ActualLog during the archiving process. If you don't, this may lead to double results in qTest.

What's next

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.

For information on how to change your qTest TestEvents, see chapter "Change qTest TestEvents".