FAQ: Frequently Asked Questions concerning QF‑Test

We - Quality First Software GmbH (QFS) - develop and distribute the software since 2001. Detailed information about QF-Test is available here.

• • Java: 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.
  • Web: QF-Test provides cross-browser testing of Web GUIs including HTML5, AJAX, DOM and Electron applications. QF-Test supports completely frameworks like Angular, React and Vue.js. Also extensions for dedicated UI toolkits are integrated in QF-Test, like Smart (GWT), ExtGWT, ExtJS, ICEfaces, jQuery UI, jQueryEasyUI, Kendo UI, PrimeFaces, Qooxdoo, RAP, RichFaces, Vaadin and ZK. Further toolkits can be integrated with little effort if required, e.g. SAP UI5, Siebel Open UI and Salesforce.
    The supported browsers are Google Chrome, Mozilla Firefox, Opera, Safari, Microsoft Edge (also Chromium based), Microsoft Edge Legacy and Internet Explorer as well as the headless browser versions of Chrome, Firefox and Edge (Chromium based)
  • Mobile applications testable via the mobile emulation mode.
  • Windows desktop applications: Win32, .Net (often C#), Windows Forms, WPF, Windows Apps and C++ (often Qt)
  • PDF documents can also be tested by QF-Test (Testing PDF documents Video).

• Windows: Windows 10, Windows 8.1, Windows 7, Server 2019, Server 2016, Server 2012 R2
• Linux: Swing and JavaFX testing is also being used in other Unix systems (Solaris, AIX, HP-UX...)
• macOS: except for SWT

Further information - also regarding JDK-/SWT-/Browser-versions - can be found in the installation chapter of the Manual.

For some time QF-Test is going to be distributed with a free Java version (JRE 8) made available by Oracle under the BCL (Binary Code License) which does not incur any costs for you or for us.
In case we bring QF-Test to Java 11 or higher, we plan to either use OpenJDK or some other free JRE or acquire a Distribution License from Oracle so that there won't be any additional costs either.

For detailed information about the QF-Test versions, please see the Release Notes.

• Continuous integration and build tools (Ant, bamboo, Maven, CruiseControl, Hudson, Jenkins, TeamCity...)
• Version management (CVS, SVN, Subversion, ClearCase, Git, Mercurial, ...)
• Issue and defect tracking (Bugzilla, JIRA, ClearQuest, TestTrack Pro, Mantis, ...)
   

Special out-of-the-box integrations are available for the following test management products:

• ALM - QualityCenter from HP
• TestBench from Imbus
• QMetry from QMetry
• Klaros from verit
• TestLink, Open Source Solution

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.

QF-Test offers lots of features (e.g. easy and stable component addressing, implicit synchronization, intuitive handling of Javascript-GUI-toolkits). The proven test approach of QF-Test applies also for web applications. 

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. Comparison of QF-Test and Selenium
All mentioned aspects also apply for derivates of Selenium as Protractor for Angular.