2018 bis heute | 2017 2016 2015 2014 | 2013 | 2012 | 2011 2010 2009 | 2008 | 2007

(ältere Archiveinträge vor 2007 nicht dargestellt, aber in der Suche enthalten)

Mailingliste - Einträge 2007

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

[QF-Test] Patch qftest-2.1.0-p3 released

  • Subject: [QF-Test] Patch qftest-2.1.0-p3 released
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: 26 Sep 2007 16:19:52 +0200

Dear QF-Test users,

the third patch against the latest QF-Test development release 2.1.0
is now available. It is provided both as a full, self-contained patch
version and as a small patch against version 2.0.3.

If you are using QF-Test 2.1 productively or have experienced any of
the problems mentioned below while experimenting with it, I strongly
advise to install the patch. If you haven't tried QF-Test 2.1 yet, now
is a good time to get the full patch-version :-)

The patch (size 260kB) is available directly from


To install the patch, simply extract the ZIP archive above the qftest
directory and restart QF-Test. During startup you should then see
version 2.1.0-p3.

For the full patch version, please visit the QF-Test download page at


For further information about patches and patch versions, please see


Best regards,

Release notes for patch version 2.1.0-p3 - September 26, 2007

New features:

* The new feature for detection of events coming from the wrong thread
  proves to be more effective than expected and many such errors have
  already been caught. The error message itself has now been improved
  to provide helpful information about the reason of the error and
  what to do about it.

Bugs fixed:

* Since version 2.1.0 QF-Test does more rigorous checking of the
  component hierarchy when working with the "Hierarchical resolution"
  setting. If the ancestors of a component in the SUT include a named
  component that is not present in QF-Test's component hierarchy, this
  is now considered a mismatch. However, this check was too strict,
  leading to recognition failures. Now QF-Test just reduces the
  respective component's probability and issues a warning.

* In very complex cases, the order of 'Dependency' nodes on the
  dependency stack after linearization could be wrong.

* If the timing was just right, a 'Wait for component to appear' node
  in the startup sequence for a WebStart based SUT could cause a

* The new Daemon API method DaemonRunCotext.getLastTest didn't work.

* The 'Procedure' swt.cleanup.closeAllMenus in the standard library
  qfs.qft did not work reliably.

* If components in a Swing SUT with Drag&Drop support were repeatedly
  removed from and added to the component hierarchy, QF-Test was
  "leaking" MouseListeners. After a few thousand iterations this could
  lead to a StackOverflowError in the SUT.

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