 |  |  |  |  |  |  |  |
| Version 7.1.4 |
Automating GUI testing is just one part of the development cycle. Requirements like automating the compilation or build
process, running tests, creating documentation or providing a deliverable package led on to a variety of
different development tools like IDEs (e.g.
Eclipse) or build tools (e.g. make,
ant, maven) or so called continuous integration systems
(like Jenkins, Cruise Control, Continuum).
In general, by use of QF-Test's command line interface as documented in chapter 23 and chapter 42 a straight forward integration with those tools should be possible.
NoteGUI tests require an active user session. Chapter Hints on setting up test systems contains useful tips and tricks to set-up your test systems. In FAQ 14 you can find technical details.
The following sections contain examples for integrations with a some of the tools mentioned above.
| | | | | | | Last update: 6/12/2024 Copyright © 1999-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.
