Tutorial as a video version, where we guide you step by step through QF-Test...
Version 8.0.1 |
When debugging a test you may want run it until it encounters an error, an exception or sometimes even a warning and then have it pause in debugging mode.
In this section you will see how this can be done while debugging the second test case.
Afterwards, when you open the debugger menu and options submenu it should look like this:
Figure 5.10: Set debugger options to pause on error |
We changed the debugger options because with default settings QF-Test will not pause on exceptions or errors, as you saw earlier on.
QF-Test will pause at the faulty node and enter debugging mode:
Figure 5.11: Test run paused by error |
The node which halted test execution will be indicated by an arrow and its symbol will be surrounded by a red square. Also, an error dialog will inform you about the failed check.
As always the run log is the key to resolving errors, so let's open it and find out how to resolve the error in the next section.
Figure 5.12: Error Dialog |
Last update: 9/10/2024 Copyright © 2002-2024 Quality First Software GmbH |
1. Functional cookies
We use functional cookies to ensure the basic functionality of the website.
2. Performance and statistic cookies
We use Matomo for analyzing and optimizing our website. Cookies permit an anonymous collection of information that help us offering you a clear and user-friendly visit of our web pages.
This cookie contains a unique, pseudonymized visitor ID internal to Matomo for recognizing returning visitors.
This cookie is used to track from which website the anonymized user proceeded to our website.
The Matomo session cookie is used to track the visitor's page requests during the session.
is created and should be then directly deleted (used to check whether the visitor’s browser supports cookies).
short lived cookies used to temporarily store data for the visit.
short lived cookies used to temporarily store data for the visit.