How you want Tosca Commander to handle errors depends on your ExecutionList. For instance, if you execute a single TestCase with a short run-time, you might prefer an immediate abort.
During the execution of complex and time-consuming ExecutionLists, however, you might want to avoid an abort at an early stage. In this case, you can implement error handling procedures that allow the execution to continue.
Specify error handling procedures
You can define how Tricentis Tosca should handle the following errors:
-
dialog failures, i.e. the interaction between Tricentis Tosca and the system under test fails
-
verification failures, i.e. the value provided by the system under test does not match the specified test value
-
exceptions, i.e. unforeseen events that keep Tricentis Tosca from executing
For each of these errors, the following procedures are available:
| Option | Description |
|---|---|
| Continue | Continue the execution of the next TestStepValue or TestStep even if the preceding TestStepValue or TestStep has failed. |
| Execute next TestCase | Do not continue with this TestCase if a TestStepValue or TestStep fails. Instead, start the execution of the next TestCase. |
| Recover | Enables Engines 3.0 Recovery. For information on how to work with Engines 3.0 Recovery, see chapter "Work with Engines 3.0 Recovery". |
You can define these error handling procedures in one of two ways:
-
If you want to apply the same procedures to all objects in your workspace, modify the respective settings in the Settings dialog.
-
If you want to apply different procedures to different objects, create test configuration parameters. The name of the parameter is the same as that of the corresponding setting, but without spaces.
Error handling parameters for Sample TestCase folder
Tricentis Tosca applies the specified procedures regardless of the cause of an error.
