Manual
New features:
-
The chapters Web testing and Web in the manual were
rewritten from scratch. The description of the central procedure
qfs.web.ajax.installCustomWebResolver can now be found in subsection 45.1.3.
-
SWT
QF-Test now supports tests for applications based on Eclipse/SWT 4.14 alias "2019-12".
-
Web
QF-Test now supports tests with Opera 64 and 65.
-
Web
QF-Test now also supports Microsoft Edge version 80 and newer.
Bugs fixed:
-
Extending a lease from the QF-Test license server could cause delays in test execution in case of temporary
networking issues.
-
Fixed a problem with setting a KeyOption via the scripting API.
-
Filtering for empty values in the search result dialog could cause an exception.
-
The
bin directories of QF-Test itself and the JRE that QF-Test runs with are no longer visible on
the environment variable PATH that the SUT sees when started from QF-Test.
-
Printing a test-suite could sometimes cause an exception.
-
When exporting the error list or some other search result for a run-log some node names were not
exported.
-
Web
XPath expressions with "-characters now work correctly.
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.
