2017 up to now  | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007

(older archive entries before 2007 are not shown here, but included in the onsite-search)

Mailing List - Entries of 2012


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[QF-Test] QF-Test version 3.4.5 released


  • Subject: [QF-Test] QF-Test version 3.4.5 released
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: Mon, 12 Mar 2012 15:41:30 +0100

Hi everyone,

for the benefit of users 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 version 3.4.5 is available for download from

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

This version mainly adds support for the new Firefox version 11 and
works around a DLL conflict problem with Firefox version 10 and higher
on Windows.

All users with a valid license for QF-Test 3.4 can upgrade directly to
QF-Test version 3.4.5.


 QF-Test and Firefox release cycles
 ==================================

It is getting increasingly difficult to keep up with the Firefox
release cycles of a major version every 6 weeks. With the release of
Firefox 10 an ongoing discussion about the applicability of this
scheme in a business context led to an Extended Support Release (ESR)
of Firefox which will receive only important security fixes over a
period of almost a year. Apparently only few users know that such a
release exists. Details about the Firefox ESR can be found at

    http://www.mozilla.org/en-US/firefox/organizations/faq/

and the current ESR version is available for download at

    http://www.mozilla.org/en-US/firefox/organizations/all.html

The main problem for QF-Test are not the short release cycles as such.
The problem is that those "major versions" are a carte blanche for
breaking with backwards compatibility and with every recent Firefox
version some other API got broken. Worse, QF-Test embeds Firefox into
a Java VM and at the current pace embedding has been declared to be of
little importance to Firefox.


What does this mean for you and your tests?
-------------------------------------------

In the short term we are trying to keep up and support every new
Firefox release. This means that you either have to stay current with
the latest QF-Test version and upgrade QF-Test at least every 6 weeks
or disable automatic updates in Firefox.

Unfortunately there is no guarantee that it will remain possible to
use Firefox the way we are using it now, so there may come a Firefox
release that is incompatible with QF-Test.

In the medium term we strongly advise to run your tests with the
Firefox ESR version.

In the long term we are working on an alternative method for
interacting with the browser that is not based on embedding. Whether a
QF-Test release will then outlast a Firefox release is anybody's
guess, but we're trying...


 Release Notes for QF-Test version 3.4.5
 =======================================

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

* Support was added for the current Firefox version 11.

* The new 'Procedure' qfs.client.sendInput in the standard library
  qfs.qft can be used to send text to the standard input of a process
  started by QF-Test.


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

* A race condition between termination of and receiving output from a
  process running on a remote machine could cause some of the process'
  output to get lost.

* Cancelling a long search in a large test-suite did not work
  reliably.

* Empty variable values in the 'Name' or 'Feature' attribute of a
  'Component' are now interpreted correctly as "ignore name" or
  "ignore feature" instead of looking for "an empty name" or "an empty
  feature" which was bound to fail.

* The QF-Test daemon was not registered at the default port when
  started without the argument -daemonport <port>.

* SUTs that use RMI with a custom implementation of the Service
  Provider Interface (SPI) failed to connect to QF-Test.

* The combination of using multiple threads with the argument -threads
  <number> in batch mode and connecting to a sub-process of the SUT
  with $(client):2 did not work correctly.

* QF-Test now works around a problem with a missing MSVC manifest in
  Firefox 10, causing an error message error message about incorrect
  loading of the C runtime library.

* Firefox 10 crashed when navigating to about:plugins.

* A download triggered at Javascript level via a link starting with
  '#' caused the browser window to close.

-- 
Gregor Schmid                                Gregor.Schmid@?.de
Quality First Software GmbH                     http://www.qfs.de
Tulpenstr. 41                               Tel: +49 8171 38648-0
DE-82538 Geretsried                         Fax: +49 8171 3864816
GF: Gregor Schmid, Karlheinz Kellerer          HRB München 140833