List Icon
Mailing list Archive

2019 up to July 2022 | 20182017  |  2016  2015 2014 | 2013

The mailing list has been closed since July 2022, but continues to serve as an archive of information about QF-Test.
If you want to stay informed about news about QF-Test, you can simply subscribe to our newsletter:
Subscribe to Newsletter  

 


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

[QF-Test] QF-Test Version 4.1.2 Released


  • Subject: [QF-Test] QF-Test Version 4.1.2 Released
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: Fri, 13 Jan 2017 14:24:00 +0100

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.

The full newsletter is also available online at

    https://www.qfs.de/en/about-qfs/news/newsletters/newsletter-2017-01-13-qf-test-412-released.html

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 4.1.2 Released
 ===============================

QF-Test version 4.1.2 is now available for download from

    https://www.qfs.de/en/qf-test/download.html

Besides bug-fixes this version also introduces a number of new
features, among them updated support for Eclipse/SWT based on the
recently release Eclipse version 4.6 SR2.


 Release Notes for QF-Test Version 4.1.2
 =======================================

New Features:
-------------
* Support for Eclipse/SWT 4.6 "Neon" has been updated for Eclipse
  version 4.6 SR2.

  Note: The mechanism for auto-scaling SWT-based UIs on high-DPI
  monitors is still deactivated by default when the SWT plugin is
  instrumented by QF-Test. The property to re-enable it has been
  renamed to swt.autoScale in SWT version 4.6 SR2.

* Resolvers are a panacea for all kinds of component recognition
  problems. To make them easier to write QF-Test 4.1 introduced an
  updated resolvers module which is now implemented by a rewrite of
  section 41.1 which makes resolvers more accessible than ever.

* The names of all registered resolvers can now be retrieved by
  calling the method resolvers.listNames().

* When performing automatic re-run of nodes, the beginning of an
  attempt is now logged as both a message and an annotation. The
  doctags for automatic re-run have been extended to enable catching a
  specific exception and to suppress log messages. See section 16.3
  for further information.

* The 'QF-Test ID' of a 'Test-case' or 'Test-set' node can now be
  retrieved at test execution time via ${qftest:testcase.id} or
  ${qftest:testset.id}.

* It is now possible to transform 'Check items' into 'Check selectable
  items' nodes and vice versa.

* If the value for the command line argument -usercfg <file> or
  -systemcfg <file> points to a directory, the configuration file is
  now read from or created within the specified directory.

* When editing options QF-Test now shows a warning in case a
  configuration file cannot be written.


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

* QF-Test now logs a warning in case the engine of a component
  retrieved by calling rc.getComponent in an 'SUT script' node does
  not match the engine executing the script. Starting with the medium
  upgrade QF-Test 4.2 this will cause an exception. Trying to pass a
  component of the wrong GUI engine to rc.overrideElement leads to an
  exception right away.

* When editing the details of a node and closing the test-suite
  without confirming the edit first, the changes were discarded.

* In case a resolver fails with an exception, other registered
  resolvers are executed anyway, like they were in QF-Test 4.0.

* QF-Test now removes temporary files created by WebDriver
  implementations.

* Cells in custom Table components with non-standard cell ordering are
  addressed correctly now.

* QF-Test could cause a deadlock in Eclipse/SWT applications with
  multiple display instances.

* When fetching the geometry of items in a web application the values
  for the parent component were retrieved instead.

* For web applications leading and trailing whitespace is now removed
  from names returned from NameResolvers.

* Automatic scrolling for image checks on items was broken in web
  applications.

--
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