QF-Test now supports testing web applications in Opera browser on Windows, macOS and Linux.
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.
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.
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
The command line argument -kill-kunning-instances 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.
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.
Closing a popup window in Firefox or closing a browser tab in any WebDriver controlled browser could
sometimes cause the entire SUT to terminate.
Frames in a popup window were not recognized correctly if the browser was connected via WebDriver.
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.
A workaround for an Electron bug now allows testing with current ChromeDriver versions.
Arguments passed to an Electron application were accidentally prefixed with "--".
Electron applications without native menus are now handled correctly.
Cleanup of browser processes has been improved even in case a browser crashes at startup.
Original third party cookie settings were not always restored correctly after closing a browser.
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.
Navigation to an anchor within the same page in JXBrowser is now handled correctly.
Event replay for JavaFX is now more resilient against unexpected window focus changes on Linux, especially
for menu item selections.
Nous utilisons des cookies "Matomo" pour l'évaluation anonyme de votre visite à note page web. Pour cela nous avons besoin de votre consentement qui est valable pour douze mois. La révocation est possbile n'importe quand sur notre page "Protection de données".