Now, any error in this use case (which is not handled by a local Event Handler within the use case) will result in one of these Event Handlers being activated. Check failed errors will mean that the test continues. Action errors, Component not found and Configuration errors will provoke a restart of the AUT . The test execution leaves the branch in which the Event Handler was nested (the use case) and carries on at the next Test Case (use case) or Test Suite .
![]() |
The app_startup Test Case is important at the beginning of each use case in case the AUT has just been restarted 5.1.3. |
Carry out these steps for each use case as you create it.
In this way, unexpected errors can be dealt with in a way that allows them to be identified later on. The test does not stop at the error, but tries to carry on at the next relevant point. This is the reason why use cases should be independent from each other - to stop further errors occurring.