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 |
Our first step is to examine the "Setup" node:
 | |||
| Figure 19.3: The Setup Node | |||
In the "Setup" node you'll see two child Sequence nodes:
Let's also have a brief look inside the Sequence: Start client if necessary:
 | |||
| Figure 19.4: The Sequence to start the SUT | |||
First you see a "Wait for client" node to double-check whether the client is already running. Only if it is not, it will be started.
The Start Windows client node starts the application (SUT) and sets up a link
between qftest and the SUT. In order to be independent of the actual installation we use
a relative path, starting from the QF-Test version directory, contained in the QF-Test
variable ${qftest:dir.version} (see manual chapter Variables).
At this point, we're ready to actually start the SUT:
Setup: Start Demo" so it is selected and still expanded (the
child nodes stay visible).
Start test run
toolbar button. This button causes the selected node to be executed.
During execution QF-Test marks the active step by use of an arrow pointer ->.
When the setup sequence is completed, our demo application "CarConfiguratorNet Form" is going to appear on the screen. As QF-Test gets back the focus after the replay action, thus being raised to the foreground, the demo application might be hiding behind it.
 | |||
| Figure 19.5: The Windows CarConfigurator Demo | |||
| | | | | | | 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.
