Manual
 

• 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.

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.
• Web Recording and replay of tests for embedded browsers has been significantly improved.
• JxBrowser is now supported in version 7, embedded into Swing, JavaFX or Eclipse/SWT applications.
• Electron Support was added for handling native dialogs in Electron applications.
• Web QF-Test now supports testing with Opera 69.
• Web 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:

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

New features:

• SWT QF-Test now supports tests for applications based on Eclipse/SWT 4.16 alias "2020-06".
• The included jsch.jar library used by the qfs.utils.ssh package in the standard library qfs.qft has been updated to version 0.1.55 in order to add support for modern Linux systems like Ubuntu 20.

Bugs fixed:

• The included WebP image compression library was rolled back to version 1.0.0 to avoid incompatibilities.
• Web Component recognition might have failed when web components had non-integer sizes.
• In rare cases calling rc.callProcedure inside the parameters of a 'Procedure call' node could lead to the global variables in the variable stack getting lost.
• The special syntax ${qftest:engine.<componentid>} that can be used to determine the engine of a component now also works if <componentid> contains a '@', '%' or '&' character.
• Selecting a single value in a run-log's error list and using "Set value as filter" twice caused an ArrayIndexOutOfBoundsException.

New features:

• The WebP image compression library was updated to version 1.1.0.
• Keyboard event input in JX Browser is now more stable.
• Contrast of toolbar icons has been improved especially for disabled buttons.
• QF-Test now supports testing with Opera 68.

Bugs fixed:

• Angular 9 is now auto-detected correctly.
• The 'CSV data file' node now correctly handles UTF-8 encoded files with BOM that start with an encapsulated complex expression.
• Windows-Tests The 'Start windows application' node can again attach to a client via a given class name (-class) in the 'Window title' attribute.
• Error handling and retry for automatic downloads of WebDriver libraries has been improved.
• Windows-Tests Recording elements with a flat hierarchy did not work.
• The PDF client is now able to check a Text component which contains only null "\u0000" characters and treats it as an empty String.

New features:

• Windows-Tests A new demo test-suite was added for the Windows 10 Calculator.
• QF-Test now supports Opera 67 with Operadriver 80.0.3987.100.
• SWT QF-Test now supports tests for applications based on Eclipse/SWT 4.15 alias "2020-03".

Bugs fixed:

• Windows-Tests When recording components for the whole window, elements within a WPF TabPanel were omitted.
• The qfs.database.executeSelectStatement procedure now works again for databases requiring an explicit db.commit() statement.
• When executing a 'Server HTTP request' node, the returned body was mistakenly not stored in a variable in case of a server error.
• JavaFX Processing JavaFX images in order to calculate a hash value could cause a NullPointerException; to get printed to the terminal.
• Windows-Tests Fixed a bug where a TextField in a Windows application might not get cleared before input.
• Windows-Tests Occasionally a ModalDialogException might get incorrectly thrown in WPF Windows applications.

Note For a detailed list of new features please see the release notes below for QF-Test versions 5.0.0.

The following major new features have been implemented for QF-Test version 5:

Changes that can affect test execution:

• The 'Server HTTP request' node now throws an exception if the status code is greater than or equal to 400. This behavior can be changed with the new attribute 'Error level if status code >= 400'.
• The options Connect via QF-Test agent and Instrument AWT EventQueue are no longer saved in the system config file and can only be changed at runtime via a script. See section 36.9 for detail.

Software that is no longer supported:

Note Please see section 1.1 for a detailed list of system requirements and supported technology versions.

• Testing of applications based on Java 6 is no longer supported.

New features:

• With the new Windows engine QF-Test can now test native Windows applications.
• Support was added for testing applications based on Java 14.
• The new 'Comment' node can be used to improve the structure and readability of test-suites and run-logs.
• It is now possible to download a file via the new 'Save response to file' attribute of the 'Server HTTP request' node.
• Windows-Tests A package for Windows applications has been added to the standard library qfs.qft.
• On Windows 10 QF-Test is now correctly displayed at scaled high resolution displays.
• Web In the manual the chapter Web testing has been revised and a section (subsection 45.1.3) describing the procedure qfs.web.ajax.installCustomWebResolver of the standard library has been added.
• The option Show message dialog after now has a setting to show a message dialog also when a test run finishes successfully.
• If the result dialog gets shown after a search the search dialog is now closed automatically.
• The new procedure qfs.util.click in the standard library qfs.qft can be used to click at an arbitrary position on the screen.
• You can now create an electron start sequence in the quickstart wizard that automatically detects the required ChromeDriver.
• When copying a 'Procedure call', 'Test call' or 'Dependency reference' node the name of the target node is now also copied as text to the clipboard.
• Web The bundled GeckoDriver has been updated to version 0.26.0.
• Web On Windows, tests with the Microsoft Edge 78 and newer are also possible in headless mode.
• Web QF-Test now supports Opera 66 with Operadriver 79.0.3945.79.
• The new variable engine.$(componentId) in the qftest special group makes it possible to find out which GUI-engine a component belongs to.
• The project tree view in QF-Test now uses a natural sort order, respecting indexes and cases.
• Data for several new mobile devices was added to the Mobile Emulation setup in the quickstart wizard.

Bugs fixed:

• An image might have been removed from the run-log in low-memory situations.
• Fixed a sporadic exception that could appear when creating a test-suite from a run-log.
• 'Finally' nodes inside a 'Try' now get executed even when an instant rerun gets triggered from within the 'Try' node.
• ImageWrapper methods now log warnings whenever the method fails.
• In very rare cases the [Ctrl] key might accidentally have stayed in pressed state after finishing replay.

B.3	QF-Test version 4

B.4	QF-Test version 3

Last update: 7/8/2020 Copyright © 1999-2020 Quality First Software GmbH