Dear QF-Test users and interested parties,

QF-Test 4.1.4 is now available for download.

Topics of this edition of our newsletter:

1. QF-Test Version 4.1.4 Released

2. Next QF-Test Training Dates and Special Webinar

3. QFS-Partner in Switzerland

4. Release Notes for QF-Test Version 4.1.4

With best regards,

Your QFS Team

P.S.: A new service from QFS: Our videos now also have subtitles (without sound, for example also in open-plan offices ...).

1. QF-Test Version 4.1.4 Released

Download-Link for QF-Test 4.1.4

Besides the usual bug fixes this release adds support for Eclipse/SWT 4.7 "Oxygen" and comes with updates for the AJAX toolkit Qooxdoo and new Selenium WebDriver libraries that support the latest versions of Chrome and Firefox.

The detailed list of differences between QF-Test version 4.1.3 to 4.1.4 can be found in the Release Notes in section 4 of this newsletter or online.

2. Next QF-Test Training Dates and Special Webinar

Training at QFS

If you prefer face-to-face training, we recommend to participate in our QF-Test training at QFS.



July 11 - 13, 2017 

November 28 - 30, 2017German

Training via Webinar

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

August 21 - 24, 2017  English (German version November 6 - 9, 2017)

Special Webinar

Martin Moser continues his popular special webinars. A special webinar session lasts about 1.5 hours and costs 125 EUR (net) per participant. Reserve your seat via or +49 8171 38648-10.


September 19, 2017 
(German version one day before)

Access the inaccessible: How to handle complex custom components in QF‑Test?
(time by arrangement)


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

3. QFS-Partner in Switzerland

QFCC is a QF-Test partner in Switzerland with more than eight years of experience in several large and small projects in renowned Swiss companies.

  • QF-Test trainings for beginners as well as experts in German, English or French language, also for individual special topics. The next training will take place August 22 – 24, 2017 in Olten.
  • Development, training and support of generic basic libraries, which ensure highest stability together with an outstanding maintainability.
  • Especially non technically experienced testers are able to create fast, complex and stable test sequences, without the need of dealing with technical details like components and their attributes etc.
  • Also perfect for automatic suite generation by test management tools such as Testbench, HP QC thanks to a consistent, lean interface.

For detailed information please visit the QFCC-website.

4. Release Notes for QF-Test Version 4.1.4

New Features:

  • Support for Eclipse/SWT 4.7 "Oxygen" has been added.
  • The embedded Selenium WebDriver framework was updated to version 3.4.0, ChromeDriver to version 2.29 (with support up to Chrome version 58) and GeckoDriver to 0.16.1 which includes support for Firefox 53 and higher.
  • Support for the AJAX toolkit Qooxdoo has been updated to latest generic class concept.
  • When continuing test execution after a break, the bottom-right view now automatically switches from the variables to the terminal.
  • Tabs in the project view now have a context menu and can be closed via a middle button click.
  • The manual chapter about modifying the CustomWebResolver for AJAX toolkits has been updated to match the latest state of development.
  • The procedure qfs.autowin.acrobat.saveAsText now automatically handles the protected mode warnings by clicking "Enable all functions".
  • By using the new method resolvers.addSpecificExtraFeatureMatcher to register an ExtraFeatureMatcher with the resolvers module, the feature name can be specified at registration time.

Bugs Fixed:

  • A possible NumberFormatException - introduced in QF-Test 4.1.3 - for batch mode execution with -verbose [<level>] has been fixed.
  • In some cases using the advanced replace dialog to replace the regular expression .* with an empty string could lead to an exception or to table entries being deleted without confirmation.
  • TestLink import scripts could have been broken in case of unicode characters in test-case names of TestLink.
  • When text containing double quotes got pasted from the system clipboard to variables or any other table, the double quotes could get lost.
  • When determining extra feature qfs:label for ComboBox, Spinner or Slider components, the tool tip could mistakenly get used instead of the nearest label.
  • The @rerun doctag was not properly evaluated in a node with additional lines in the comment.
  • The command line argument -plugindir <directory> was ignored in batch mode.
  • Selecting a component via the chooser might create an explicit reference, even though the component was part of an included test-suite.
  • Explicit component references within the local test-suite were not taken into account when looking for unused components.
  • Analyzing references of relative test-calls didn't work correctly.
  • Duration and realtime are now updated correctly when merging run-logs.
  • In case the fallback library for Jython version 2.5 is installed, the Jython package cache now gets activated by default as it was in QF-Test version 4.0.
  • If the option "Intelligent scrolling in trees" was deactivated, there were cases when the selected node was not scrolled visible in the tree at all, e.g. after a search or when entering the debugger.
  • In some cases custom mappings of classes were not taken into account for testing with AJAX resolvers.
  • The libraries required for hardware accelerated graphics in the embedded Chrome browser were removed again, because they could cause a crash when opening a popup window.
  • Caching of non-standard attributes in the embedded Chrome browser was broken in QF-Test version 4.1.3, which could lead to component recognition issues in special cases.
  • Many debug messages from GeckoDriver and Mozilla Marionette are now filtered from the shared terminal.
  • In some cases clearing the browser cache during startup could cause Edge to hang for up to several minutes.
  • The entry for showing available methods was missing from the menu for JavaFX component recording.