 |  |  |  |  |  |  |  |
| Version 8.0.1 |
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 24 and chapter 43 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: 9/10/2024 Copyright © 1999-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.
