[QF-Test] Almost there: QF-Test 4.0 Release Candidate 1 released

• Subject: [QF-Test] Almost there: QF-Test 4.0 Release Candidate 1 released
• From: Gregor Schmid <Gregor.Schmid@?.de>
• Date: Fri, 04 Jul 2014 14:31:20 +0200

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.

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

QF-Test 4.0 is nearly complete and enters the final release phase with
this first Release Candidate. Depending on user feedback and barring
last-minute problems we hope to get QF-Test 4.0 released within July.


 QF-Test 4.0.0-rc1 released
 ==========================

QF-Test version 4.0.0-rc1 is now available for download from

   http://www.qfs.de/en/qftest/download.html

Highlights of QF-Test 4 include:

* New GUI engine: JavaFX

* Support for Chrome browser on Windows

* Improved support for Java WebStart and Applets

* Support for the AJAX framework jQuery UI

* Generic classes for components of all GUI engines

* Multi-level sub-item concept with QPath similar to XPath

* Support for embedded browsers: Java FX WebView and JxBrowser 4

* Improved user interface with colored syntax highlighting

* New package for client-side ssh connections

For a detailed list of innovations since QF-Test version 3.5 please
see the release notes for QF-Test versions 4.0.0-beta1 through
4.0.0-rc1 in the QF-Test manual or at

    http://www.qfs.de/en/qftest/relnotes.html

Changes between QF-Test version 4.0.0-beta3 and 4.0.0-rc1 are listed
in the release notes below.


 License updates for QF-Test 4
 =============================

To ease the transition QF-Test version 4 can be used with a license
for QF-Test version 3.5 until August 31, 2014. Please make use of this
transition period to update your QF-Test licenses to version 4.0.

Users with a valid Maintenance Agreement are entitled to this major
upgrade for free. Without Maintenance Agreement the fee for upgrading
from version 3.5 to version 4.0 is 30% of the current license price.

Please note that Chrome support is automatically included in
QF-Test/web whereas JavaFX support in QF-Test/fx is a new GUI engine
that must be purchased separately or as an add-on. Evaluation licenses
automatically include support for the JavaFX engine, users with a
commercial license should request an evaluation license if they want
to give QF-Test/fx a try.


 Release Notes for QF-Test version 4.0.0-rc1
 ===========================================

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

* QF-Test now supports multi-level sub-items for addressing components
  within an item. A typical example is a TextField within a table cell
  that can now be addressed as table@Header&row@:TextField. The syntax
  is extremely powerful with the potential to mix XPath-like syntax
  with QF-Test's component representation.

* The former 'Id' attribute of 'Window' and 'Component' nodes is now
  called 'QF-Test ID' in order to disambiguate it from the various
  kinds of IDs used by the supported GUI engines.

* Generic classes are now also implemented for standard HTML nodes
  even without a dedicated AJAX resolver.

* Support for the AJAX toolkit RichFaces was updated to RichFaces
  version 3.

* Support for Eclipse/SWT has been updated for Eclipse version 4.4
  "Luna".

* The Nebula Grid component is now supported by default and
  automatically recognized.

* It is now possible to define a directory for saving temporary
  run-logs in interactive mode via the option "Directory for
  run-logs". During QF-Test startup this directory can be specified on
  the command line via -runlogdir <directory>.

* The new option "Directory map for test-suites" can be used to map
  directories for test-suites. This is very useful when working with a
  run-log from a machine with a different file layout (e.g. Windows
  vs. Unix) because with the correct directory mapping QF-Test can
  locate a test-suite without manual help.

* There are two new special variable groups to conveniently escape
  special characters. ${quoteitem:...} deals with characters like '@'
  or &' in a textual sub-item index and ${quoteregexp:...} handles
  '.', '(', '[' etc. in a regular expression.

* It is now possible to specify a directory as a bookmark. When such a
  bookmark is selected, the file selection dialog is opened directly
  for this directory.


Bugs fixed:
-----------

* Multiple instances of the Chrome browser can now run simultaneously
  on one machine.

* Performance, stability and supported feature set for browsers
  embedded via Java FX WebView and JxBrowser were improved.

* The AJAX toolkit RAP does not use the 'ID' attribute of DOM nodes to
  define IDs, so the option "Eliminate all numerals from 'ID'
  attributes" had no effect for RAP. This has been fixed, so that with
  the option activated, numerals are now removed from IDs generated
  for RAP elements. In case this causes problems with existing tests,
  simply deactivate the option "Eliminate all numerals from 'ID'
  attributes".

* With support for Java FX and its Swing InterOp embedding
  capabilities as well as support for embedded browsers, SUT clients
  often have more than one GUI engine. This caused problems with 'SUT
  script' nodes in the standard library qfs.qft which were relying on
  the default GUI engine. All procedures with 'SUT scripts' now have
  an optional parameter named guiengine which is predefined correctly,
  so that for example a 'Procedure' in the 'Package' qfs.web
  automatically works correctly in an embedded browser. In the
  exceptional case of an SUT client with more than one GUI engine of
  the same kind you can define the guiengine parameter to address a
  particular engine.

* After introducing generic classes, replay was broken in case an
  anonymous inner class was manually assigned for a component.

* During dependency resolution, 'Parameter default values' of
  'Dependency' nodes were not correctly bound.

* Performance of test execution in interactive mode suffered from
  repaint issues caused by the new syntax highlighting in the tree
  view.

--
Gregor Schmid

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

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

• Prev by Date: Re: [QF-Test] including captured stderr or stdout from SUT scripts in the test report
• Next by Date: [QF-Test] Vaadin check readonly status of TextField
• Previous by thread: [QF-Test] JavaFX embed
• Next by thread: [QF-Test] Vaadin check readonly status of TextField
• Index(es):
  • Date
  • Thread