01. What is QF-Test?
02. What GUI technologies are supported for testing?
03. What are QF-Test's outstanding features?
04. Which platforms is QF-Test available on (system requirements)?
05. What releases of QF-Test are currently available and what do they contain?
06. How about integration with other tools?
07. Who uses QF-Test already?
08. We are testing our website already with Selenium. Do I need QF-Test then?
Why GUI test automation?
Evaluation and licensing
12. Is a trial version available for download?
13. Do I need anything else?
14. So how do I get a license?
15. Which GUI technology/technologies do I need to buy?
16. How much does QF-Test cost?
17. Does QF-Test need an additional license server?
Support, training and feedback
QF-Test is a professional tool for the creation, execution and management of automated system and load tests for Java and Web applications with a graphical user interface (GUI). QF-Test has been developed and distributed by Quality First Software GmbH (QFS) since 2001. Detailed information about QF-Test is available on the page QF-Test.
For Java based applications the full toolkit set is covered starting with the traditional Swing (including Applets, Webstart, ULC, CaptainCasa), its successor JavaFX (JavaFX SubScene components as well) and also SWT, the Standard Widget Toolkit from Eclipse, including Plugins and RCP (Rich Client Platform) applications. Furthermore QF-Test provides cross-browser testing of Web GUIs including HTML5, AJAX (Angular (up to Angular 5), Smart (GWT), GXT / ExtGWT, ExtJS, ICEfaces, jQuery UI, jQuery EasyUI, Kendo UI, PrimeFaces, Qooxdoo, RAP, RichFaces, Vaadin, ZK). Further toolkits can be integrated with little effort if required, e.g. SAP UI5, Siebel Open UI and Salesforce. PDF documents can also be tested by QF-Test. The supported browsers are Google Chrome, Firefox, Internet Explorer, Safari and Microsoft Edge as well as headless browser for Chrome and Firefox.
If you don't know exactely which AJAX toolkit you are using, read the following technical FAQ.
Easy to use:
QF-Test supports Java version 7, 8, 9 as well as 10 and on:
Further information - also regarding JDK-/SWT-/Browser-versions - can be found in the installation chapter of the Manual.
For background information about the QF-Test versioning scheme, please see The life cycle of a QF-Test version.
As QF-Test provides multiple interfaces (batch and daemon mode, scripting, ...) and uses XML as primary data format a flexible combination and communication with other tools is possible (among others Quality Center, load testing tools like Noeload, Scapa TPP):
Special out-of-the-box integrations are available for the following test management products:
More than 1,000 companies from over 50 countries, ranging from small ones to the largest IT service providers worldwide are using more than 7,000 licenses. See here for examples: References.
With Selenium developers can quickly create web-tests. However, if tests get more complicated or should be easily maintainable, and when also non-developers are part of the testing team, we recommend switching to QF-Test. To control modern browsers, QF-Test uses, like Selenium the WebDriver-standard. It is also possible integrate existing Junit-based Selenium tests via Unit test steps or via the Selenium API in scripts directly in visual test procedures.
The tool price of QF-Test in comparison to Selenium is just a small part of the test project costs. The main factor is manpaower. So the effectivity of implementing and maintaining tests is playing a decisive role. And QF-Test already has maintenance, support, further development, bug fixes etc. included.
Though indispensable, unit tests can only test small parts of a system in isolation (steering-wheel OK, motor OK). GUI based testing exercises an application as a whole (steering-wheel and motor taken together don't guarantee roadworthiness). See Benefits for developers.
Automated software testing reduces time and costs spent on quality assurance. Comprehensive automated tests, executed regularly during software development, will detect bugs at an early stage. The reproducible security thus achieved ensures higher quality and shorter time to market at lower maintenance expense. A tool with reliable component recognition and low maintenance effort is a precondition, however.... and a few other conditions (tester, test design...).
Thanks to the low price for licenses and the good usability of QF-Test you can start quickly with efficient testing and have a high return on investment (blog). Just compare the costs for licenses with common costs for developers' or testers' wages and the costs of bugs detected after release - not to mention the damage to your company's reputation. See Benefits for decision-makers.
Yes. You can download the trial version here.
Normally a license file is required to run QF-Test. It will run without a license, but it will not let you save any files or load any files that were not provided by Quality First Software GmbH. This is sufficient for getting a first impression, working through the tutorial and making a first attempt at running your application under QF-Test. To go beyond that, you'll need a license file.
You can obtain a free trial license valid for 4 weeks by filling in the request form.
QF-Test licenses can be purchased specifically for the GUI technologies actually needed. In order to determine the GUI technologies for your application, open your test-suite(s) and run all your client(s) via QF-Test. After having executed your tests, please open the 'Clients' menu. There you can see the GUI technologies used in  brackets. In the example there are two clients running using [Swing] and [Web]; all combinations out of [Swing], [Swt], [FX] and [Web] are possible.
License types and prices for QF-Test are listed on the page Prices. The QF-Test licenses are "floating" within a network and persistent (except leasing licenses of course).
No, not necessarily. QF-Test handles multi user license management for local networks by itself, provided that IP multicast works. For floating licenses across multiples sites and in case of restricted networks, a license server is available.
Enhancement requests should preferably be sent to the mailing list (see 18.), but they are also welcome anytime at firstname.lastname@example.org.