[QF-Test] QF-Test 4.1 Release Candidate 2 available

• Subject: [QF-Test] QF-Test 4.1 Release Candidate 2 available
• From: Gregor Schmid <Gregor.Schmid@?.de>
• Date: Fri, 02 Sep 2016 11:30:56 +0200

Dear QF-Test users,

the second (and hopefully last) release candidate for QF-Test 4.1 is
now available for download. Since rc1 the WebDriver support has
significantly improved, with much better performance and updated
drivers for Edge and Firefox 48. Groovy was updated to version 2.4.7
and the documentation and release notes are now mostly up-to-date.

This release candidate has an extended expiration date and is valid
until the end of January 2017 (indefinitely with a QF-Test 4.1 license).

You can download QF-Test 4.1.0-rc2 directly from:

    https://archive.qfs.de/pub/qftest-4.1.0-rc2.exehttps://archive.qfs.de/pub/qftest-4.1.0-rc2.tar.gzhttps://archive.qfs.de/pub/qftest-4.1.0-rc2.ziphttps://archive.qfs.de/pub/QF-Test-4.1.0-rc2.dmg

Just pick the variant that suits you best.

You can install the 4.1 release candidate in parallel to your QF-Test
4.0 installation and your QF-Test 4.0 license is sufficient to run it.
The upgrade to QF-Test 4.1 will be free if you have a valid
maintenance contract.

After installation, please be sure to read the Release Notes in
appendix B of the manual. They contain important information about
major changes and potential incompatibilities as well as cross-links
to new features in the manual.

Detailed changes since 4.1-rc1 are listed at the end of this mail.


 Highlights in QF-Test 4.1
 =========================

* The new browser connection mode based on Selenium WebDriver adds
  support for additional browsers including Firefox 44 and up, Edge
  and Safari as well as Chrome now also on Linux and macOS.

* Selenium scripts can now be run from inside QF-Test and mixing of
  QF-Test and Selenium tests is possible. See section 40.2 for how to
  access the WebDriver API from 'SUT script' nodes.

* QF-Test now officially supports Swing, JavaFX and Web testing on
  macOS. A dedicated installer is available.

* Jython was updated to version 2.7.0. QF-Test now requires at least
  Java 7 unless Jython is rolled back to version 2.5.1 as explained in
  subsection B.1.2.

* Groovy was updated to version 2.4.7. QF-Test now requires at least
  Java 7 unless Groovy is rolled back to version 2.1.0 as explained in
  manual subsection B.1.2.

* By using our new license server mechanism, licenses can now be
  floated globally instead of just across the local network. If
  interested, please get in touch with QFS via sales@?.de.

* 64 bit browsers are now supported on all systems.

* Support was added for the AJAX framework Kendo UI.

* Many existing AJAX resolvers were updated and generalized and are
  now easier to customize.

* In QF-Driver mode QF-Test can now synchronize web tests based on
  outstanding HTTP requests. This is controlled via the options
  "Synchronize with HTTP requests", "Timeout for HTTP request
  synchronization (ms)" and "Extended HTTP request timeout for new
  documents (ms)".

* For web QF-Test now supports component resolution using XPath and
  CSS selectors. See Addressing via XPath and/or CSS-Selectors for
  details.

* The new connection mechanism for Swing works out-of-the-box in many
  of the problematic cases with Java WebStart, applets or custom
  EventQueues. It can be disabled via the option Instrument AWT
  EventQueue.

* The maximum execution time for sequences, test-cases, test-sets or
  whole batch runs can now be limited via the attribute 'Execution
  timeout (ms)' and the command line argument -timeout <milliseconds>.

* Run-logs can now be merged.

* Event replay for all engines now uses an approach we call Generic
  Retry that better handles timing issues, especially components that
  vanish or get replaced just while QF-Test was trying to access them.

* Variable expansion is now also possible in a static context so that
  jumping from a procedure call like checksFor${qftest:testcase.name}
  to the correct procedure simply works. QF-Test caches the most
  recent variable values from the last execution so this is useful
  even for dynamic bindings.

* The various data nodes like 'Database' or 'Excel data file' can now
  also be executed outside a data driver context in order to bind the
  values directly as variables instead of iterating over the sets. In
  that case the 'Name' attribute of the node also defines the name of
  the properties group into which the variables are bound.

* Eclipse plugin - Special launch configurations that combine starting
  the SUT, launching QF-Test and possibly running initial test-steps
  directly from Eclipse - Not officially published yet. If interested,
  please get in touch with QFS via <support@?.de>

* Updates to the QF-Test manual include new chapters about
  keyword-driven testing and load-testing as well as a major rewrite
  of important topics and more comprehensive documentation for QF-Test
  pseudo DOM API.


 Changes since 4.1.0-rc1
 =======================

New features:
-------------

* Groovy was updated to version 2.4.7. QF-Test now requires at least
  Java 7 unless Groovy is rolled back to version 2.1.0 as explained in
  manual subsection B.1.2.

* WebDriver support is significantly improved and performance is much
  better. Firefox 48 and higher now also work as Selenium was upgraded
  to support for Firefox Marionette.

* For web QF-Test now supports component resolution using XPath and
  CSS selectors. See Addressing via XPath and/or CSS-Selectors for
  details.

* The procedure qfs.utils.xml.compareXMLFiles was improved with better
  filtering and the ability to ignore missing tags or attributes when
  specified in the "noCheck" parameter.

* On Windows, 'Text input' nodes can now be replayed for JXBrowser.

* The procedure qfs.utils.email.sendEmail in the standard library
  qfs.qft now also supports attachments.

* Jython was modified to catch and suppress NotImplementedErrors
  caused by implementing only parts of an interface which was OK with
  Jython 2.5. This behavior can be modified by setting the system
  property qftest.workarounds.abstractMethodsHandling to one of the
  values "ignore", "warning", "error" or "exception".


Bugs fixed:
___________

* Uncaught exceptions on the JavaFX application thread were correctly
  reported by QF-Test, but in some cases they were not passed on which
  might hide bugs in the SUT or at least prevent testing the SUT's own
  handling of uncaught exceptions.

* Occasionally a call to DaemonLocator.locateInstance(long timeout)
  might locate a daemon, but "forget" it again before returning the
  result after the timeout was reached.

--
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: Re: [QF-Test] Unable to get the state of a checkbox
• Next by Date: [QF-Test] Column result not right by empty RAP-Table
• Previous by thread: [QF-Test] Unable to get the state of a checkbox
• Next by thread: [QF-Test] Column result not right by empty RAP-Table
• Index(es):
  • Date
  • Thread