QF-Test has continuously supported Java Swing (the traditional GUI toolkit, with is part of every Java version of Oracle since 1997) since its very beginning in 1999 as a tool for automated GUI testing.
QF-Test can test Swing applications with an embedded browser like e.g. JxBrowser. You can access both, the Java and the Web part of the application.
JavaFX is the successor of Swing and an integral part of Java 8. With Java 11 JavaFX was moved out of the JDK into the open source project OpenJFX. Since 2014 QF‑Test supports this GUI technology and provides advanced testing support including complex components like trees and tables. QF‑Test can test JavaFX applications with an embedded browser like e.g. JxBrowser or WebView. You can access both, the Java and Web part of the application.
When you migrate your application from Java Swing to JavaFX, you can reuse Swing GUI tests in QF-Test for JavaFX automated testing with little effort.
Java GUI tests for applications based on the Standard Widget Toolkit (SWT), including Eclipse plug-ins and the Rich Client Platform (RCP). QF-Test has continuously provided support for this toolkit since 2008.
"After evaluating a number of Java Swing automated testing tools, we found QF-Test to be the only one that managed to execute Java GUI tests on multiple platforms without platform dependency issues.
Let me add three sentences about your support: "This is what I call a response time! Great job! No wonder that your company is such a success :)."
Bojan Lozinsek, Projektmanager
Hermes Softlab, Maribor, Slovenia
"My personal opinion is that QF‑Test is still the best JAVA GUI test tool in market."
Saša Milošević, QA engineer
NIRI Intelligent Computing, Serbia
"QF-Test was the only automation tool that worked on our specific, highly customized Swing framework."
Isis Bauquis, Test engineer
Sword Linkvest SA, Switzerland
"I evaluated about 10 tools for automated Java GUI testing. Our table models were very complex therefore for evaluation of the tools I designed few tests/criteria which dealt with cells' content and images. Neither of the tools could perform all tests. I contacted specialists from technical support, they either admitted that their tools could not do some specific tasks, or they tried to offer workarounds, which would be an option if I would not find a tool that 'does it all.'
When I evaluated QF-Test it passed all my tests. Still I was a little bit hesitant because its scripting language was Jython, and learning a new language is a considerable effort, though an extensive array of standard nodes was very simple to use. Some of other tools had scripting language which I already knew; nevertheless eventually I made my mind and selected QF-Test reasoning that reliable performance was more important than my learning efforts."
Matt Ezren, QA developer
Creditex, Inc., New York, USA