Error Handling Flags
- Dhiraj Chandanshive (Unlicensed)
An Error Handling Flag is a pre-defined behaviour of a test case or a test suite execution when any step fails.
You can set Error Handling Flags at two levels:
- Task Level: To set flags for tasks in the Test Case Editor screen
- Test Case Level: To set flags for test cases in the Test Suite screen.
By default, an Error Handling Flag is set to Continue. To change the flag for a task or a test case, double-click its flag and select the flag you want to apply.
Points to Know
- Error Handling Flags are applied only for error conditions and not for defects. For example, execution status of following step is "Defect" and not "Error".
CompareString "a" "ab" "true"
- Error Handling Flags do not apply to the invalid IF/ELSE IF steps.
Error Handling Flag Settings in a Test Case
In a test case, you can set the Task Level error handling flags for all the tasks to define the execution behaviour of the test case in a suite execution and even in a dry run.
The following table shows how flags can be set in tasks of a test case.
| Icon | Flag Name | Description |
|---|---|---|
| ExitTCIteration | If any task step fails, QAS skips executing the current test case iteration and starts executing the next iteration. If there is only one TC iteration, then the test case execution stops. |
 | ExitTask | If any step of this task fails, QAS skips all the remaining steps of the current task, and starts executing the next step or task. |
| Continue | If any step of this task fails, QAS does not exit and continues executing the remaining steps and tasks. |
Error Handling Flag Settings in a Test Suite
In a test suite, you can set the Test Case Level error handling flags for all the tasks to define the execution behaviour of the test suite.
The following table shows how flags can be set in test cases of a test suite.
| Icon | Flag Name | Description |
|---|---|---|
 | ExitTCIteration | If any step fails, QAS skips executing the current test case iteration and starts executing the next iteration. If there is only one TC iteration, then the QAS starts executing the next test case. |
| ExitSuite | If any step fails, QAS stops executing the whole suite. |
 | Continue | If any step fails, QAS does not exit and continues executing the remaining steps and tasks. |
The following table shows the suite execution behaviour when a flag is set for task and also for its its test case.
Flag for Task on Test Case Screen | Flag for Test Case on Suite Screen | Screen Settings Considered | Result |
|---|---|---|---|
Continue | Continue | TC | Continue |
ExitTask | Continue | TC | ExitTask |
ExitTCIteration | Continue | TC | ExitTCIteration |
Continue | ExitTCIteration | Suite | ExitTCIteration |
ExitTask | ExitTCIteration | Suite | ExitTCIteration |
ExitTCIteration | ExitTCIteration | Suite | ExitTCIteration |
Continue | ExitSuite | Suite | ExitSuite |
ExitTask | ExitSuite | Suite | ExitSuite |
ExitTCIteration | ExitSuite | Suite | ExitSuite |