Medium Upgrade QF-Test 4.6 Released

Dear QF-Test users and interested parties,
QF-Test 4.6.0 is now available for download.

Topics of this edition of our newsletter:

1. Highlights of QF-Test Version 4.6
2. Next Training Dates
3. New Blog Articles and YouTube Video
4. Support Form
5. Release Notes for QF-Test Version 4.6.0


With best regards,

Your QFS Team

1. Highlights of QF-Test Version 4.6

Download-Link for QF-Test 4.6.0

  • Support for Opera browser
  • Support for new Microsoft Edge browser based on Chromium
  • Support for SWT 4.12 alias 2019-06
  • Preview: Testing native Windows applications

The detailed list of changes from QF-Test version 4.5.2 to 4.6.0 can be found in the Release Notes in section 5 of this newsletter or online.

Users with a valid maintenance contract can use this version without updating their license. Without maintenance the upgrade needs to be purchased but can be tried until July 31 with a license for QF-Test version 4.5. The preview for the upcoming QF-Test Windows engine requires a trial license in either case.

2. Next Training Dates

Training at Our Site

[Translate to English:] QF-Test Schulung bei QFS

We recommend to participate in our face-to-face QF-Test training at our site (compact course) in small groups. Here are all dates for 2019.

DateLanguage
July 02-04, 2019German
October 15-17, 2019German

Training via Webinar

QF-Test Webinarschulung

You can save travel time and expenses by participating in one of our trainings via webinar:

DateTraining via webinarPrice
time by arrangementCompany webinar training
(exclusively for your company)
individual offer

And of course you can always book training or consulting individually for you and your company or on-site.

4. Support-Form

Another new feature is our support form referenced directly from QF-Test with fields that help us answering your support questions more efficiently. You can find this link in QF-Test via "Help" → "Contact the support team...".

Support Form Menu action
Support request form
Support request form
Support request form
Support request form
Support request form
Support request form
Support request form
Support request form
Support request form
Support request form
Support request form
Support request form
Support request form
Support request form
Support request form
Support request form
Support request form
Support request form
Support request form
Support request form
Support request form
Support request form
Support request form
Support request form
Support request form
Support request form
Support request form
 

5. Release Notes for QF-Test 4.6.0

New Features

  • 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 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 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.loghashentries=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.
  • 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 process 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.