[QF-Test] QF-Test 4.2.3 released

• Subject: [QF-Test] QF-Test 4.2.3 released
• From: Gregor Schmid <Gregor.Schmid@?.de>
• Date: Thu, 03 May 2018 16:47:37 +0200
• Delivered-to: qftest-list@?.net

Dear QF-Test users,

for the benefit of those that don't receive our newsletter the
technical details of new QF-Test releases are also announced on this
mailing list. My apologies if you receive this information twice.

This release comes with an enhanced autowin package in the standard
library qfs.qft that now also makes use of Windows UI Automation for
some very basic test automation of Windows applications. It also adds
support for the Shadow DOM Web API, brings updates for the latest
browsers and a few more smaller features as well as several bug fixes.

The full newsletter is also available online at

    https://www.qfs.de/en/about-qfs/news/newsletters/newsletter-2018-05-03-qf-test-423-released.html

Should you be interested in subscribing to the full newsletter please
send an informal email with subject "Subscribe Newsletter" to
<newsletter@?.de>.


 Release Notes for QF-Test 4.2.3
 ===============================

New Features:
-------------

* The embedded Selenium WebDriver framework was updated to version
  3.11.0 and ChromeDriver to version 2.38 (with support up to Chrome
  version 67), and Mozilla GeckoDriver to version 0.20.1 which adds
  support for Firefox 59. The 32bit Linux version of ChromeDriver was
  removed from QF-Test as it is no longer supported by the Chrome
  development team. If needed, the last available version (2.33) can
  be downloaded manually from the ChromeDriver archive.

* QF-Test now supports the Shadow DOM API and thus interaction with
  web elements that are embedded in an open ShadowRoot.

* To bridge the gap until a full Windows engine is available for
  QF-Test the qfs.autowin package in the standard library qfs.qft has
  been extended to make use of Windows UIAutomation. It includes
  several new procedures to automate simple tests for native Windows
  applications. Please see chapter 26 for detailed information.

* When moving the mouse cursor over the menu entry for a connected
  client in the »Clients« menu, the main window of the respective
  client gets highlighted.

* The new variable group ${idlocal:...} is similar to ${id:...} with
  the added effect of enforcing component lookup in the test-suite
  that is current at the time of expansion. See section 7.5 for
  further information.

* The debug information for component recognition in the run-log is
  now more readable and - like other text fields in the run-log - can
  be opened in an external editor via the new new keyboard shortcut
  [Shift-Control-Return].


Bugs Fixed:
-----------

* The deprecation warning dialog for Java WebStart in Java 9 or higher
  is now handled automatically by QF-Test

* When refactoring or analyzing test-suites, rc.callProcedure calls
  are now taken into account everywhere, i.e. in every variable
  attribute and not just in script nodes.

* A data-driver iteration inside a 'Test-step' can now be interrupted
  via a 'Break' node like any other node iteration.

* Firefox in QF-Driver mode could crash on Linux when processing
  certain non-UTF-8-encoded strings.

* For Chrome in QF-Driver mode right button mouse clicks did not work
  correctly in qooxdoo applications.

* A missing "http:" protocol header in a proxy auto-config URL is now
  gets automatically corrected.

* Getting the name for an embedded Swing window from the enclosing
  JavaFX SwingNode now also works with Java update 8u171.

-- 
Gregor Schmid

E: gregor.schmid@?.de
T: +49 8171 38648-11
F: +49 8171 38648-16

Quality First Software GmbH | www.qfs.de
Tulpenstr. 41 | 82538 Geretsried | Germany
GF Gregor Schmid, Dr. Martina Schmid, Karlheinz Kellerer
HRB München 140833

• Prev by Date: [QF-Test] Override existing pdf
• Next by Date: Re: [QF-Test] Override existing pdf
• Previous by thread: [QF-Test] Override existing pdf
• Next by thread: [QF-Test] Access QF-Test test failure statistics from Jenkins
• Index(es):
  • Date
  • Thread