QF-Test Medium Version 5.1 Released

New Features

• Support was added for testing applications based on Java 15.
• The JRE ditributed with QF-Test has been updated to Zulu OpenJDK Version 8_252.
• Recording and replay of tests for embedded browsers has been significantly improved.
• JxBrower is now supported in version 7, embedded into Swing, JavaFX or Eclipse/SWT applications.
• Support was added for handling native dialogs in Electron applications.
• QF-Test now supports testing with Opera 69.
• Support for the web framework Qooxdoo has been updated for Qooxdoo version 6.
• HTML reports can now be customized via JavaScript in the form of a user.js. See subsection 20.1.4 for details.
• The automac module now provides methods for simulating keyboard and mouse events. See chapter 47 for further information.
• The root node of a test-suite now also has a 'Name' attribute that is shown in the tree.
• The new option Enable 'Local variable' attribute by default determines, whether the attribute 'Local variable' gets pre-activated in newly created nodes.
• The procedure qfs.utils.dragAndDrop in the standard library qfs.qft has a new optional parameter eventDelay to control replay speed.
• It is now possible to convert a 'CSV data file' node into an 'Excel data file' node and vice versa.
• Test-suite tabs can be moved left or right using the keyboard shortcuts [Shift-Ctrl-Page up] and [Shift-Ctrl-Page down].

Bugs Fixed

• The procedure qfs.web.browser.settings.setLocale now also works for WebDriver connections to Chromium based browsers.

Changes that can affect test execution

• Due to the updated JRE in the QF-Test installation, graphical elements and graphs in the PDF client may be painted with slightly different anti-aliasing. This can lead to errors in 'Check image' nodes. Given that such problems cannot be ruled out for future JRE updates you should set the 'Algorithm for image comparison' attribute of affected nodes to "algorithm=similarity;expected=0.98".
  The JRE update can also cause communication problems between QF-Test and the QF-Test license server in case the license server is run with a very old Java version that cannot cope with the key length required for SSL in current Java versions. In that case it is best to update the license server to the current QF-Test version and use its included JRE.
• The library jniwrapper is no longer loaded by default because our old jniwrapper version crashes QF-Test on newer JDKs. Modules with native dependencies like autowin have been rewritten to no longer depend on it and all references to jniwrapper have been removed from the standard library qfs.qft.
  If you still have script nodes in your test-suites that depend on jniwrapper you should try to reimplement these in order to remove that dependency. Please get in touch with our support if you need help.
  As an interim solution you can get such scripts to work again (on older JDKs where jniwrapper does not crash) as follows:
  Copy the files from misc/jniwrapper in the QF-Test installation directory to qftest in the QF-Test plugin directory. To locate those directories, open the »Help«-»Info« dialog and look for dir.version and dir.plugin on the 'System info' tab.
  Add either a Jython server script to your startup sequence with
  from com.jniwrapper import DefaultLibraryLoader
from java.io import File DefaultLibraryLoader
.getInstance().addPath\
(File(rc.lookup("qftest", "dir.plugin") + "/qftest"))
  or the following Groovy variant
  import com.jniwrapper.DefaultLibraryLoader
DefaultLibraryLoader.getInstance().addPath
(new File(rc.lookup("qftest", "dir.plugin") + "/qftest"))
• The ChromeDriver library for old Chrome versions (older than 72) is not bundled wit QF-Test anymore.
• Testing applications running on Java 7 ist still supported in this QF-Test version. However, support for Java 7 has been deprecated and will be removed in QF-Test version 5.2.