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 |
First of all we need to activate debugging mode. There are several ways
to do so. One of them is to set a breakpoint at the node where we want to
have a closer look. When the test is being executed and QF-Test comes to the break
point it will then
pause and switch into debugging mode. The pause button 
will then
be activated.
.
 | |||
| Figure 5.1: Set break point | |||
 | |||
| Figure 5.2: Start test run | |||
 | |||
| Figure 5.3: Remove break point | |||
Instead of using the keyboard shortcut [Ctrl-F8] ([⇧⌘-B] on macOS) you may also set or unset a breakpoint by clicking the node and selecting the »Debugger«-»Breakpoint on/off« menu item, or alternatively right-clicking the node and selecting the »Breakpoint on/off« context menu item.
Again, you can see the little arrow, which now marks the next node to be executed, called the current node. When entering debugging mode QF-Test also navigates to the current node, in case it had not been visible, and selects it, highlighting it blue.
The menu option »Debugger«-»Clear all breakpoints« is useful to remove all breakpoints set in your test suite.
There is no limit to the number of breakpoints you can set in your test suite, but note that breakpoints are not saved with the test suite.
| | | | | | | 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.
