Manual
New features:
-
SWT
QF-Test now supports tests for applications, which have been developed using Eclipse/SWT 4.13 alias "2019-09".
-
Windows-Tests
The defined user interface scaling of windows is now optionally taken into account when executing windows tests.
-
Electron
If required, QF-Test now automatically downloads support for new versions of the Electron framework.
-
Web
Improved testing perfomance of WebDriver controlled browsers on Windows systems.
-
Web
Improved performance of the CustomWebResolver for Primefaces.
-
Windows-Tests
During Windows-tests, it is now possible to check for table components a whole row at once.
-
Jumping from resultlist to suite now also works with "Return".
-
Web
Improved item scrolling performance with WebDriver browsers.
-
Web
Updated the embedded geckodriver to version 0.25.0.
-
Web
Supporting tests with Operadriver 76.0.3809.132.
Bugs fixed:
-
JavaFX
The Java FX WebView tests had problems interacting with web frames, which are fixed now.
-
Windows-Tests
A hierarchy of modal windows could falsely trigger a ModalDialogException during Windows tests.
-
Web
On systems without active user session, replay of web mouse clicks could lead to a NullPointerException.
-
Web
Web page load was not detected when the web page or framework undefined the javascript dialog methods.
-
When extensively expanding variables outside a testrun, QF-Test might have used all available memory.
-
Fixed a rare NullPointerException which could happen when using rc.checkImageAdvanced() in combination with an image in image search.
-
The standard procedure "qfs.autowin.acrobat.savePDF" could sometimes stop with message "filename field cannot be determined" because of slow network connections when opening the save dialog and cloud targets activated.
-
Web
Changed the URL for remotely loaded javascript in the "qfs.web.general.integrateFirebug" procedure.
-
Web
The automation infobar of Google Chrome is now also hidden during webtests with Chrome version 76 and higher on Windows.
-
Swing
If the QF-Test agent is activated two times by an erroneous client specification, the connection to the SUT is now established nevertheless.
-
The qfs.database.executeSelectStatement procedure now also works for databases that require an explicit db.commit() statement.
New features:
-
Testing of Java 13 based SUTs is now supported.
-
Support was added for Electron 6.
-
Support was added for OpenWebStart.
-
Web
The embedded Chrome browser used for QF-Driver mode was updated to CEF version 73.
-
Web
The Opera browser is now supported up to version 62 which uses a different scheme for the associated
WebDriver.
-
Web
For web testing on Windows in WebDriver mode, display scaling is now taken into account at Windows level
as well as for browser-based zooming.
-
The new method
rc.getPropertyGroupNames lists the names of non-special property groups for
which values are bound.
Bugs fixed:
-
Web
The profile directory for testing with Microsoft Edge had the wrong name.
-
Web
Closing a popup window could crash the Opera browser.
-
Web
Text input for Microsoft Edge was always positioned at the end of the field.
-
Web
A possible deadlock in Internet Explorer when loading resources for a web page was fixed.
-
Web
Stopping a browser controlled via WebDriver could sometimes cause an (otherwise harmless) error message
in the QF-Test terminal.
-
JavaFX
When using a custom ItemResolver for JavaFX clicks to the center of the item were not replayed correctly.
-
SWT
On Linux SWT instrumentation was performed even when not required.
New features:
-
Web
QF-Test now supports testing web applications in Opera browser on Windows, macOS and Linux.
-
Web
QF-Test now also supports the new Microsoft Edge browser based on Chromium.
-
Support was added for Eclipse/SWT version 4.12 alias "2019-06".
-
Via the new methods
print and println that were added to the qf
module it is now possible to print messages directly to QF-Test's terminal from both 'Server script'
and 'SUT script' nodes, irrespective of whether the SUT output gets redirected or not and
whether there's a RunContext available or the code is part of a resolver during recording.
-
The new command line argument
-license.waitfor <seconds> allows waiting for a QF-Test license to become
available during startup.
-
For better conformance with regulations for protection of personal data the
licenseserver.log
file written by the QF-Test license server now contains hashes instead of user name, host name or IP address.
This can be turned off via the new command line argument -licenseserver.hashlogentries=false.
-
A "mouseButton" parameter was added to the various
clickAtImage procedures in the qfs.autoscreen package of the standard library qfs.qft.
-
The new shortcut [Shift-Ctrl-Right] can be used in the parameters table
of 'Procedure call' nodes to quickly create a forward - i.e.
x -> $(x) -
of the current variable value for the selected table rows.
-
The embedded JUnit Jupiter library was updated to version 5.4.2.
Bugs fixed:
-
Importing procedures from large test-suites could lead to an
OutOfMemoryError.
-
Closing QF-Test in check recording mode without killing the SUT process would leave the SUT in a completely
unusable state.
-
The command line argument
-killRunningInstances could inadvertently terminate QF-Test processes on
other machines in the local network provided those were started with -allowkilling.
-
Auto-saving test-suites could accidentally trigger re-compression of images. For test-suites with many or
large images this could slow down QF-Test noticeably.
-
Reading the license file from a slow network drive could occasionally fail.
-
Opening a test-suite in Windows explorer via the context menu of the suite tab failed in case the
file name contained spaces.
-
In rare cases waiting for a component during SUT startup could trigger a
ClientNotConnectedException instead of the expected ComponentNotFoundException.
-
The procedure
qfs.autowin.acrobat.saveAsText was updated for Acrobat version
19.12.20034.1161 and newer.
-
Variables bound in the data driver of a 'Test-step' were lost when using "continue from here" inside
the 'Test-step'.
-
Output of the -licenseserver.dump* batch commands was missing information for the JavaFX engine. In
addition to fixing that, information about Windows engine licenses was added, the "AWT" columns were
renamed to "Swing" and information for engines that are not available in the server license is no longer
displayed. These changes all apply to the interactive license administration tool as well.
-
Web
Closing a popup window in Firefox or closing a browser tab in any WebDriver controlled browser could
sometimes cause the entire SUT to terminate.
-
Web
Frames in a popup window were not recognized correctly if the browser was connected via WebDriver.
-
Web
Performance for web tests has been improved, for both QF-Driver and WebDriver connection modes. The
effects are very dependent on the specific web application.
-
Web
A workaround for an Electron bug now allows testing with current ChromeDriver versions.
-
Web
Arguments passed to an Electron application were accidentally prefixed with "--".
-
Web
Electron applications without native menus are now handled correctly.
-
Web
Cleanup of browser processes has been improved even in case a browser crashes at startup.
-
Web
Original third party cookie settings were not always restored correctly after closing a browser.
-
Web
In a web application 'Fetch text', 'Fetch index' and 'Fetch geometry' nodes could fail
with an internal error when trying to determine the value while the target node got dynamically removed
from the DOM. Now the operation is retried instead.
-
Web
Navigation to an anchor within the same page in JXBrowser is now handled correctly.
-
JavaFX
Event replay for JavaFX is now more resilient against unexpected window focus changes on Linux, especially
for menu item selections.
