Tutoriel en version vidéo: Nous vous guidons pas à pas à travers QF-Test...
Working with a Sample Testsuite
Creating your own testsuite
Writing a procedure
Components
Using the Debugger
Variables and Procedure Parameters
The Standard Library
Control structures
It's time to start your own application
 |  |  |  |  |  |  |  |
| 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 14.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 14.11: Test run stopped 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 14.12: Error Dialog | |||
| | | | | | | Last update: 9/10/2024 Copyright © 2002-2024 Quality First Software GmbH |
1. Cookies fonctionnels
Nous utilisons des cookies fonctionnels pour garantir la fonctionnalité de base du site web.
2. Cookies de performance et de statistique
Nous utilisons Matomo pour analyser et améliorer notre site web. Des cookies permettent une collection anonyme des informations qui nous aident à vous offrir un visite clair et facile à utiliser de nos pages web.
This cookie contains a unique, pseudonymized visitor ID internal to Matomo for recognizing repeat visitors.
This cookie is used to track from which website the anonymized user proceeded to any page or sub-page.
The Matomo session cookie is used to track the visitor's page requests during the session. The cookie is automatically deleted at the end of each session (website visit), at the latest after one day.
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.
