QF-Test 4.1.1 Released

Dear QF-Test users and interested parties,

QF-Test 4.1.1 is now available for download.

Topics of this edition of our newsletter:

1. QF-Test Version 4.1.1 Released

2. Next QF-Test Training Dates via Webinar and Special Webinars

3. QFS at the OOP Conference in Munich

4. Release Notes of QF-Test Version 4.1.1

Thank you and with best regards,

Your QFS Team

1. QF-Test Version 4.1.1 Released

Logo QF-Test 4.1.1

Download-Link for QF-Test 4.1.1

Besides fixing several bugs, this release also includes a number of new features, among them a handy new filter for quickly locating test-suites in large projects and improved key bindings for macOS.

The detailed list of differences between QF-Test version 4.1.0 to 4.1.1 can be found in the Release Notes in section 4 in this newsletter or online at https://www.qfs.de/en/qftest/relnotes.html#4.1.1

Users with a valid QF-Test license of 4.1 can directly update to QF-Test version 4.1.1. Licenses for QF-Test 4.0 are also still valid for the interim period until 2016-02-28.

2. Next QF-Test Training Dates via Webinar and Special Webinars

QF-Test training webinar

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

DateLanguage
Feb 27 - March 02, 2017  English

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 webinar@remove-this.qfs.de or +49 8171 38648-10.

DateContent
January 24, 2017 
(German version one day before)

Component recognition for Java - Optimization with resolvers and generic components (time by arrangement)

Component recognition for Web and AJAX applications - optimization via CustomWebResolver (time by arrangement)

Announcement: In March 2017 Martin Moser will hold the webinar about the release of QF-Test 4.1 because of high demand again.

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

3. QFS at the OOP Conference in Munich

Logo OOP Munich

In the end of January 2017 the OOP conference (Object oriented programming) will take place in Munich. Software quality has now also reached the heart of this developer conference: For the first time the German Testing Board is going to be a gold sponsor.

From 2017-01-31 to 2017-02-02 Martin Moser and other QFS colleagues will present the latest version of QF-Test at the QFS stand. We are looking forward to your visit! You can also make an appointment in advance for a demo or specific questions.

4. Release Notes for QF-Test Version 4.1.1

New Features:

  • The project view now comes with a filter at the top of the tree that matches on test-suite names and limits the hierarchy accordingly, which is very useful for quickly finding test-suites in large projects.
  • On macOS all keyboard shortcuts should now be conforming to Mac standards and use Mac-friendly modifier keys.
  • Selenium WebDriver was updated to version 3.0.1.
  • The documentation and samples for keyword driven testing have been extended with a new example for behavior driven testing (BDT).
  • The parameters for the @rerun doctag were extended to include a newerrorlevel=keep option and the new keepfirst parameter.
  • The 'Execution timeout' attribute is now also available for 'Test-step' nodes.

Bugs Fixed:

  • QF-Test did not start if the Java version for QF-Test was still instrumented by an older QF-Test version (pre 4.1). Though JRE instrumentation has been deprecated for many years, such a case is still possible. QF-Test now detects that situation and helps with deinstrumentation of the JRE.
  • The test for busy panes was missing when performing a check using the generic retry mechanism introduced in QF-Test 4.1.0.
  • When interactively selecting a component for an event node the current target was not pre-selected in the chooser dialog.
  • Trying to update failed checks from the error list after closing the originating run-log caused an unexpected exception.
  • When using the databinder.bindList API for performing data-driven testing, QF-Test now ignores empty lists instead of running a single iteration without data.
  • When importing test results into TestLink, skipped test-cases are now correctly reported as skipped.
  • The former WebDriver API was renamed to WebDriverConnection to avoid confusion with Selenium's WebDriver object.
  • The error message for expiration of a -timeout <milliseconds> command line argument of a batch call now clearly refers to the -timeout <milliseconds> argument instead of the root node of the test-suite.</milliseconds></milliseconds>
  • In large projects editing component IDs in parameter tables no longer causes delays while QF-Test is looking for the component to highlight.
  • When searching through a project with an invalid regular expression many errors messages were shown instead of just one.
  • Short timeouts for visible false checks on components were not honored.
  • If the option "Instrument AWT EventQueue" is active, QF-Test now establishes a connection with the awt:security engine in case Java WebStart shows an authentication dialog. Please note that in such a case the 'GUI engine' attribute of the 'Wait for client to connect' node must be set to awt:security.
  • Class resolution for AJAX toolkits was broken for some special cases.
  • The editable check didn't work for TextFields in the PrimeFaces toolkit.
  • When recording a click that triggers an alert dialog in WebDriver mode, the order of the recorded events was not always correct.
  • Auto-detection for AJAX toolkit resolvers has been improved. It now prints concise messages to the terminal and cleanly handles the case when no toolkit is detected.
Videos Downloads Documentation Buy Free Trial