List Icon
Archiv Mailingliste

2019 bis Juli 2022  2018  | 2017 2016 2015 | 2014 | 2013

Die Mailingliste ist seit Juli 2022 geschlossen, dient aber weiterhin als Informationsarchiv zu QF-Test.
Wenn Sie über Neuerungen zu QF-Test informiert bleiben wollen, können Sie einfach unseren Newsletter abonnieren:
Newsletter abonnieren


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

[QF-Test] QF-Test Version 4.2.0 Released


  • Subject: [QF-Test] QF-Test Version 4.2.0 Released
  • From: Gregor Schmid <Gregor.Schmid@?.de>
  • Date: Wed, 10 Jan 2018 14:21:46 +0100
  • Delivered-to: qftest-list@?.net

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-10-qf-test-42-released.html

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


 Highlights of QF-Test Version 4.2
 =================================

* Java 9 support

* Testing of PDF documents

* Additional scripting language JavaScript

* Support for Angular includes UI toolkits Bootstrap and AngularJS
  Material

* Support for Smart GWT

* Dedicated nodes for static and live unit tests

* Headless web-testing

* Testing of REST services

* The QF-Test tutorial was rewritten from scratch.


 Backwards Compatibility and System Requirements
 ===============================================

Please see section 1.1 of the manual at 

    https://www.qfs.de/en/qf-test-manual/lc/manual-en-user_installation.html#usec_install_system

for a detailed list of system requirements and supported technology versions.


QFS is taking pains to maintain backwards compatibility even in case
of substantial changes. For further information please see:

* New Windows compliant setup:

    https://www.qfs.de/en/qf-test-manual/lc/manual-en-user_installation.html#usec_install_windows

* Changes that can affect test execution:

    https://www.qfs.de/en/qf-test-manual/lc/manual-en-history.html#incompatibilities_4_2

* Software that is no longer supported

    https://www.qfs.de/en/qf-test-manual/lc/manual-en-history.html#sec_N1CE69


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

New Features:
-------------

* QF-Test can now test applications based on Java 9. This includes
  support for the new Java 9 module system ("Project Jigsaw") without
  having to resort to the "Big Kill Switch", i.e. the command line
  argument --illegal-access.

* Testing PDF documents like a normal application in a dedicated PDF
  viewer with textual and graphical checks for individual elements.

* JavaScript was added as new scripting language equal to Jython and
  Groovy for 'Server script' and 'SUT script' nodes. This encompasses
  the ECMAScript 8 standard and all QF‑Test scripting modules like
  resolvers, rc or autowin are available in JavaScript.

* Support was added for the popular AJAX framework Angular, including
  support for the UI toolkits Bootstrap and AngularJS Material.

* Support was added for the AJAX toolkit Smart GWT.

* The new 'Unit test' node can run JUnit tests and integrate the
  results in the QF-Test run-log and report. Tests can be implemented
  in Java or as scripts and run statically or dynamically in a 'live'
  SUT as an alternative to writing mocks.

* Support was added for headless web-testing using the headless
  versions of Chrome and Firefox.

* The 'Server HTTP request' node now supports testing REST services
  via the additional methods HEAD, PUT, DELETE, TRACE and CONNECT and
  it is now possible to specify custom headers for the HTTP request.

* The QF-Test tutorial was rewritten from scratch.

* The re-implemented Quickstart Wizard combines a concise workflow
  with an improved design.

* The »Help«-»Info« dialog has a new tab "System info" that shows many
  QF-Test settings and system information.

* Attributes like the 'Condition' condition of an 'If' node which are
  evaluated by the Jython interpreter now have syntax highlighting and
  support for code completion.

* The embedded Chrome browser used for QF-Driver mode has been updated
  to CEF version 57.

* The command line argument -run now also works for interactive mode
  to directly start test-execution when running QF-Test. This is
  complemented by the new -suitesfile <file> argument that can be used
  to specify a text-file containing the test-suites and tests to
  execute.

* There are new commands available for controlling QF-Test from the
  command line. The new batch argument -interruptRunningInstances can
  be used to suspend tests running in the local machine. Similarly,
  -killRunningInstances will cleanly terminate running instances,
  including interactive ones, provided they were started with the
  argument -allowkilling. Cleanly here means that batch tests are
  stopped, dependencies rolled back and run-logs are saved.

* The new Windows setup program for QF-Test adheres to the current
  Windows conventions for placing different kinds of files in various
  locations. There's still an option to use the old layout with all
  files in a single place.

* On macOS, application arguments can now be configured from within
  QF-Test.

* You can now specify a macOS app directly as the 'Executable'
  attribute of an 'Start SUT client' node.

* A 'Sequence' node can now also be transformed into a 'Loop' or
  'While' node.

* Calls to deprecated procedures or test-cases are now also stroke
  through in the tree view.

* The 'Load properties' node now supports loading property files
  encoded as UTF-8 via its new attribute 'File encoding is UTF-8'.

* Components in the SUT are now highlighted automatically when
  clicking on a component or event node in QF-Test's tree,
  irrespective of whether the node was already selected or not. If
  automatic highlighting is deactivated via the option Highlight
  selected component in the SUT you can now trigger it explicitly via
  the context menu of component, event or check nodes as well as
  QF-Test component IDs in parameter tables and scripts.

* The boolean values in the 'Extra feature' attributes of a
  'Component' or the 'Items' attribute of a 'Check items' node can now
  make use of variables. Simply double-click the respective table cell
  to edit the value.

* The new webResolvers module enables implementing resolvers in
  JavaScript that run directly in the browser. See section 42.2 for
  detailed information and examples.

* The extra feature qfs:label now also applies to Window and Dialog
  components.

* There are several new (or newly documented) command line options for
  overriding the directories that are relevant to QF-Test, including
  -userdir <directory>, -systemdir <directory>, -jythondir
  <directory>, -groovydir <directory>, -javascriptdir <directory>,
  -plugindir <directory> and -logdir <directory>.

* Several definitions for directories relevant for the QF-Test
  installation have been added to the qftest property group, e.g.
  ${qftest:dir.log} for the directory into which run-logs are saved
  automatically. See section 7.5 for a detailed list.

* The sort order of parameter tables like the 'Variable definitions'
  attribute of a 'Procedure call' node can now be reset to the order
  of the called node via the table's context menu.


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

* Conversion into a regular expression used on a 'QF-Test component
  ID' attribute now correctly differentiates between the ID and the
  sub-item syntax.

* On Ubuntu Linux taking SUT thread dumps and terminating
  sub-processes of the SUT did not work.

* Unicode characters outside the Basic Mulitilingual Pane (BMP) are
  now handled correctly.

* TooltipResolvers are now also called for non-Swing AWT components.

* The procedure qfs.web.general.integrateFirebug now loads Firebug via
  https instead of http which prevents issues with mixed content.

* In some cases the text of a MenuItem in a web application could
  mistakenly include the text of its sub-MenuItems as well.

* Creating many embedded WebView or SWT Browser instances could lead
  to a memory leak.

* Running a JavaFX based SUT via WebStart could cause some
  IllegalAccessExceptions.

* Names for the tabs of a JavaFX TabPanel now take possible so-called
  Graphic elements into account. 


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