ChromeDriver was updated to version 2.43 (for Chrome up to version 71).
In QF-Test version 4.4.0 PDF tests accidentally required a Swing license. Now they work again regardless of
the licensed engines.
Running QF-Test in batch mode with multiple threads using -threads <number> now also works for PDF and unit
The QF-Test daemon did not work when using a keystore and sharing the daemonport with the normal QF-Test
port for SUT communication.
With Chrome 70 on Windows the screen location of elements was incorrectly computed after a navigation
so that hard events might miss their target.
For Safari version 12 or newer the connection can no longer established via the Safari extension because
it is no longer supported by Apple. SafariDriver is now used instead which only supports replay but no
The print dialog control for Chrome on macOS is now handled correctly.
Event recording was broken for Eclipse/SWT legacy versions 3.6 and older.
WINDOW_MOVED events for the file chooser of the PDF client are now filtered reliably.
The new automac module can be used to control native macOS applications at script level. It
is accompanied by procedures in the package qfs.automac of the standard library
qfs.qft. See chapter 51 for further information.
Support was added for Eclipse/SWT version 4.9 alias "2018-09".
The 'Unit test' node can now run unit tests using the JUnit 5 "Jupiter" engine.
New text checks for PDF documents add the ability to check the text of an entire page with a single
'Check text' or 'Check items' node.
GeckoDriver was updated to version 0.23.0 (for Firefox up to version 62) and ChromeDriver
to version 2.42 (for Chrome up to version 69).
The arguments of TestRunListener methods can now easily be converted to Json objects and for
a TestRunEvent a call to getNode().getComponentId() now returns the QF-Test
component ID of the current step. See section 52.7 for details.
Auto-filling the comment of a procedure could accidentally drop @author information and other doctags.
In special cases the call to rc.toServer in a Jython 'SUT script' node could cause
The result of a 'Fetch index' step for first-level child nodes of a Tree or TreeTable component in
a web application wasn't always correct.
With Internet Explorer a download triggered in a popup window could remain incomplete.
Computing the name of an embedded Swing Frame based on the containing JavaFX SwingNode now also works with
We use "Matomo" cookies to anonymously evaluate your visit to our website. For this we need your consent, which is valid for twelve months. A revocation, so-called opt-out, is possible at any time on our privacy page.