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 TestEvent(s).

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

Run all tests in your qTest TestEvent(s)

To run all tests in your qTest TestEvent(s), trigger the execution in one of the following ways:

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

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 test(s) 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.

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