Quality First Software GmbHgradient
Quality First Software GmbH
ProfessionalTest Automation
Home|Contact|Deutsch
QF-Test  –  The GUI Test Tool for Java and Web Demo VideoDownloadQF-Test BookletQF-Test

Release notes

This document lists changes to QF-Test since version 3.0.

For background information about the QF-Test versioning scheme, please see The life-cycle of a QF-Test version.

The latest version of QF-Test is available for download here.

Release notes

Version 4.0.2-p2 - December 2, 2014

New features:

bullet 
Support for Firefox has been updated to match the public release of Firefox version 34 and support for Firefox version 35 has been added.

Bugs fixed:

bullet 
In QF-Test version 4.0.2-p1 the user agent string returned by Firefox browsers was incomplete.

Version 4.0.2-p1 - November 11, 2014

Bugs fixed:

bullet 
Support for Firefox version 33 has been updated to cope with the new Firefox versioning scheme introduced with Firefox 33.1.

Version 4.0.2 - October 22, 2014

New features:

bullet 
Support was added for Firefox versions 33 and 34.
bullet 
Support for Eclipse/SWT 4.4 "Luna" has been updated for the Eclipse 4.4 SR1 release.
bullet 
Support for Java FX has been updated for some FX changes in the Java update 8u20.
bullet 
The QF-Test Agent mechanism is now compatible with the tighter security restrictions introduced with Java updates 8u25 and 7u71/7u72.
bullet 
Java FX Charts are now fully supported with improved representation of the component parts and various dedicated checks.
bullet 
Support for the AJAX toolkits Ext JS and PrimeFaces has been updated to include support for Ext JS version 5 and PrimeFaces version 5.
bullet 
The backwards compatibility for recording components with generic classes into test-suites with pre-QF-Test-4.0 components has been extended to include support for merging such components via the import feature.
bullet 
The 'Try'/'Catch'/'Finally' construct has been extended to support an 'Else' node which is executed in the case when the contents of the 'Try' are executed cleanly without throwing an exception.
bullet 
'Window' nodes now also support 'Extra feature' attributes, just like 'Component' and 'Web page' nodes.
bullet 
It is now possible to override the way how QF-Test determines generic classes by implementing a GenericClassNameResolver.
bullet 
There is now a dedicated section in the manual explaining how to quickly implement resolvers for AJAX web toolkits that are not yet supported out-of-the-box.

Bugs fixed:

bullet 
In some cases the record button could remain active even though no SUT client was connected to QF-Test anymore.
bullet 
On a Windows machine with only a 64bit Java installed, QF-Test now explicitly searches for the 64bit Java installation in "C:\Program Files" in case it does not find a javaw.exe program on the default PATH.
bullet 
The procedures in the qfs.utils.ssh package did not use the correct default known_hosts file.
bullet 
The 'Excel data file' node now handles the character encoding of old-style .xls files correctly.
bullet 
The runid was not stored correctly in a run-log in case a batch test was run with split run-logs disabled via the command line argument -splitlog=false.
bullet 
Check visible tests for items could incorrectly fail with an IndexNotFoundException instead of reporting a passed or failed check.
bullet 
The QF-Test editor for the proc-builder configuration file could get corrupted while recording new procedures and editing the file in parallel.
bullet 
The context diff for a failed 'Check items' was incomplete in some rare cases.
bullet 
Startup for WebStart and applets has been made more robust, including a fix for a ClassCastException occasionally seen in applets.
bullet 
The newly introduced support for custom tab components assigned via JTabbedPane.setTabComponent could break replay of existing recordings.
bullet 
Cells of a Nebula Grid component can now be recorded correctly from a scrolled location and also addressed via negative indexes.
bullet 
Recording of events on FX controls embedded in an SWT based SUT no longer produces duplicates and checks can now be recorded normally for such FX controls.
bullet 
The default compatibility mode for Internet Explorer 10 and up has been fixed and the user agent returned by IE for document.documentMode now always correctly reflects the current compatibility mode.
bullet 
Waiting for a dynamically inserted FRAME and its document to be loaded now works correctly in all browsers.
bullet 
QF-Test now uses a different method for determining the geometry of TEXT nodes in all browsers that is less invasive and more efficient. The old method could occasionally interfere with Javascript code in web pages.
bullet 
There was a tricky race condition mostly seen in connection with a special kind of download, triggered by opening a temporary web page which automatically closes immediately. QF-Test now handles such situations and the respective download cleanly.
bullet 
The Chrome browser now displays a confirmation dialog when a window gets closed and an onbeforeunloadhandler is defined.
bullet 
Component and procedure recording in the Chrome browser is considerably faster.
bullet 
The embedded Chrome browser can now show videos.
bullet 
Double click events are now correctly recorded in the Chrome browser.

Version 4.0.1 - August 28, 2014

New features:

bullet 
The JavaFX TreeTableView component, which was introduced with Java 8, is now fully supported.
bullet 
QF-Test now supports recording and checking of tabs for JTabbedPane components which use the setTabComponent method to implement some or all tabs as actual components.
bullet 
If the 'Encoding' attribute of a 'CSV data file' node is set to "UTF-8", QF-Test now tries to determine itself whether the file starts with a Byte Order Mark (BOM) or not and handle it accordingly. QF-Test also treats an 'Encoding' attribute with "x-UTF-8-BOM" or "x-UTF-8-No-BOM" correctly, even though Java has no direct support for these encodings.
bullet 
When moving the mouse over any image stored in a test-suite or run-log, QF-Test now displays the (X,Y) coordinates and color values of the associated pixel.

Bugs fixed:

bullet 
The timeout value of the option "Wait for non-existent item (ms)" was ignored in some cases, e.g. when performing checks with a timeout.
bullet 
An 'Extra feature' using variables for a regular expression value could mistakenly trigger a BadRegexpException.
bullet 
In QF-Test version 4, leading and trailing whitespace is removed from sub-item names. Playback compatibility was provided for most cases, but not all. This should now work consistently.
bullet 
The context diff for a failed 'Check selectable items' node in the run-log now includes visual representation for the expected and actual selected states and is shown correctly also in cases where there are differences only in the selected state.
bullet 
Formulas in Excel files that return boolean values or that switch cell types more than once are now handled correctly by the 'Excel data file' node and the procedure qfs.utils.files.readExcelFile.
bullet 
In a hybrid Swing and JavaFX application, handling of Swing JTable components was partly broken due to interference from the JavaFX ItemResolver for tables.
bullet 
Recording of items in a multi-rooted JavaFX tree (i.e. a tree with its primary root node hidden) is now correct.
bullet 
Component highlighting was broken when recording checks in an Eclipse / SWT application.
bullet 
There were still dependencies on a newer version of glibc left in the instrumentation files for 64bit versions of Eclipse, causing failures on some Linux systems with an old version of glibc - for example RHEL 6.5.
bullet 
Tests with Firefox versions 27 and 28 did not work correctly.
bullet 
Text checks for table headers were broken in some web tables.
bullet 
A proxy auto-config (PAC) file defined in a procedure call of qfs.web.browser.settings.setProxy is now interpreted correctly.
bullet 
The Chrome browser now displays a confirmation dialog when a window gets closed and an onbeforeunload handler is defined.
bullet 
Javascript errors in the Chrome browser are no longer printed to the terminal but written to the run-log.
bullet 
In the Chrome browser coordinates inside an IFRAME were displaced if the frame had a border defined, leading to offsets when highlighting components and to image check failures caused by insufficient automatic scrolling.
bullet 
Drag&Drop via the procedure qfs.web.general.dragFromTo now also works with Chrome.
bullet 
Clearing the browser cache did not work with Firefox version 32.
bullet 
The procedure qfs.web.table.getRowCount could fail in the rare case when the first column of a table is invisible.

Main new features in QF-Test version 4

For a detailed list of new features please see the release notes for QF-Test versions 4.0.0-beta1 through version 4.0.0 below.

The following major new features have been implemented for QF-Test version 4:

bullet 
New GUI engine: JavaFX
bullet 
Support for Chrome browser on Windows
bullet 
Improved support for Java WebStart and applets
bullet 
Support for the AJAX framework jQuery UI
bullet 
Uniform generic classes for components of all GUI engines
bullet 
Multi-level sub-item concept with QPath, similar to XPath
bullet 
Support for embedded browsers
bullet 
Improved user interface with colored syntax highlighting
bullet 
New package for client-side ssh connections

Version 4.0.0 - July 31, 2014

New features:

bullet 
Support was added for Firefox versions 31 and 32.
bullet 
A more user-friendly way of updating a QF-Test license is now available via the menu »Help«-»Update license...«.
bullet 
When opening a Jython or Groovy terminal for an SUT client, the command history from the most recently created Jython or Groovy terminal is copied. This makes it easier to try out the same scripts when repeatedly restarting the SUT.
bullet 
When importing QF-Test results into TestLink it is now possible to use the 'QF-Test ID' for associating test-cases and to omit the platform.
bullet 
After starting QF-Test the record button now has a help icon that leads to the quickstart wizard for launching an SUT. This feature is intended to assist first-time users that often wonder why they cannot start recording right away.
bullet 
The procedure qfs.web.ajax.installToolkitResolver now allows specifying default versions for automatically detected AJAX toolkit resolvers. This prevents inadvertent updates to versions with potential incompatibilities in newer QF-Test versions.
bullet 
The default severity level for Javascript errors in web pages has been changed to 'Warning'. Current browsers simply ignore Javascript problems by default so that treating those as an error caused too much irritation. The setting can be changed via the option "How to handle Javascript errors in a Web application".

Bugs fixed:

bullet 
On Linux systems like RHEL 6.5 with an old version of glibc, instrumented 64bit versions of Eclipse failed to start. This dependency on a newer version of glibc has been removed.
bullet 
When the QF-Test agent was enabled, an Eclipse / SWT application with embedded Swing components connected as two SUT clients instead of one client with two GUI engines.
bullet 
Column header cells in JavaFX tables are now addressed correctly.
bullet 
CheckBox elements inside JavaFX table cells or tree nodes are now recorded with the new @:CheckBox item syntax.
bullet 
The check for the editable state of TextField, PasswordField and TextAreas nodes was missing for web clients.
bullet 
A selection in a ComboBox that initiated a navigation to another page could cause Internet Explorer to crash.
bullet 
Check recording in the browser did not work in an area covered by an invisible IFRAME.
bullet 
Event synchronization for the AJAX toolkit Ext JS now handles modal dialogs correctly.
bullet 
Replay of text input for INPUT elements of type "number" has been fixed.
bullet 
When defining proxy settings for Internet Explorer via the qfs.web.browser.settings.doStartupSettings procedure, proxy.pac files were not handled correctly.
bullet 
In newer Java and Browser versions the startup behavior of applets has changed, sometimes causing two JRE versions to start up simultaneously. Depending on timing, this could cause the real applet to connect as $(client):2 instead of $(client). QF-Test now works around this problem by connecting to an applet only after it has become visible.
bullet 
The "All lines" check for Swing JTextArea components was not recorded correctly when clicking below the first line of text.
bullet 
There are now two different text checks for JEditorPane components that display HTML, "Text" and "HTML source". In many cases the check against the plain, displayed text is more useful than the former default check for the HTML source code. Also, the text check for JEditorPane components that display RTF has been fixed.
bullet 
When canceling an edit in the detail view or adding of a new node, QF-Test now checks whether modifications were made and asks for confirmation before discarding those. This confirmation dialog can be suppressed via the option "Ask before discarding detail modifications".
bullet 
When toggling the disabled state of the selected node, modifications made but not confirmed in the detail view were silently discarded.

Version 4.0.0-rc1 - July 4, 2014

New features:

bullet 
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.
bullet 
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.
bullet 
Generic classes are now also implemented for standard HTML nodes even without a dedicated AJAX resolver.
bullet 
Support for the AJAX toolkit RichFaces was updated to RichFaces version 3.
bullet 
Support for Eclipse/SWT has been updated for Eclipse version 4.4 "Luna".
bullet 
The Nebula Grid component is now supported by default and automatically recognized.
bullet 
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>.
bullet 
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.
bullet 
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.
bullet 
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:

bullet 
Multiple instances of the Chrome browser can now run simultaneously on one machine.
bullet 
Performance, stability and supported feature set for browsers embedded via JavaFX WebView and JxBrowser were improved.
bullet 
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".
bullet 
With support for JavaFX 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.
bullet 
After introducing generic classes, replay was broken in case an anonymous inner class was manually assigned for a component.
bullet 
During dependency resolution, 'Parameter default values' of 'Dependency' nodes were not correctly bound.
bullet 
Performance of test execution in interactive mode suffered from repaint issues caused by the new syntax highlighting in the tree view.

Version 4.0.0-beta3 - May 13, 2014

New features:

bullet 
Support was added for Firefox version 30.
bullet 
Procedure recording is now fully supported for JavaFX.
bullet 
For web applications based on the AJAX framework ZK QF-Test now resolves the original developer-assigned IDs and uses them as names for components.
bullet 
Support for the Chrome browser is continuously improving. Up- and download are now fully supported as well as login dialogs, closing of browser windows, key and text input including modifiers and cursor position. Also, there now is a custom profile folder to separate testing from normal use with support for cookie and cache cleanup, locale and proxy settings.
bullet 
Embedded browsers in JavaFX WebView or via JX Browser are also making headway and multiple embedded browsers in one window are now handled correctly.
bullet 
Simple but very useful: The dialog shown when an error or exception occurs during a test now has an additional button for jumping directly to the respective node in the run-log.
bullet 
A check was added for the checked state of a CheckBox in JavaFX table cells, tree nodes and list entries.
bullet 
The new procedure qfs.web.general.dragFromTo supports HTML5 style drag and drop operations without blocking the application, alternatively at Javascript level or via hard events.

Bugs fixed:

bullet 
The introduction of generic classes for SWT caused a serious performance issue that has been fixed.
bullet 
For SWT QF-Test refused to replay hard events on negative coordinates which, however, are necessary to reach a window on a second monitor placed to the left of the main screen on Windows.
bullet 
The print dialog is now shown correctly in Firefox.
bullet 
In very special cases running a test in a QF-Test daemon could fail due to a missing engine license even though the license was available.

Version 4.0.0-beta2 - April 11, 2014

New features:

bullet 
Generic classes are now also implemented for Swing and SWT.
bullet 
QF-Test records generic class, custom class and system class as extra features named qfs:genericclass, qfs:class and qfs:systemclass respectively. This is useful information and can be used to switch individual components to a more specific or less specific class. In case the generic class also has a more specific sub-type QF-Test also records the extra feature qfs:type, e.g. "PanelTitle" for a Label that is the title of a TitledPanel.
bullet 
Supported standard functionality for Chrome now includes support for downloads, handling prompt and confirm dialogs as well as getting and setting the cursor position in text fields which is required for recording mouse events relative to a character position and for 'Text input' nodes which insert text into the middle of existing text.
bullet 
Support for embedded browsers now includes JavaFX WebView and JxBrowser 4. Though this is still work in progress, basic capture and replay for mouse events already works.
bullet 
When started from QF-Test Chrome now also automatically accepts SSL certificates for HTTPS connections.
bullet 
It is now possible to choose between different layouts of the test-suites in the selection dialog for 'Procedures'.

Bugs fixed:

bullet 
Thanks to improved focus management replay for JavaFX on Linux should be more reliable now, especially selection of menu items.
bullet 
Replaying hard mouse click for the middle or right button did not work correctly with JavaFX.
bullet 
An Excel 2010 sheet with a cross-sheet reference to a pure number is now handled correctly by the 'Excel data file' node.

Version 4.0.0-beta1 - March 26, 2014

New features:

bullet 
JavaFX is the successor of Swing as the standard UI Toolkit in Java 8. QF-Test version 4.0 introduces the new product line QF-Test/fx that fully supports testing JavaFX applications. This GUI engine is nearly complete. Missing at this point is recording of procedures and support for handling the embedded WebView as a full-featured QF-Test Web engine is incomplete.
bullet 
Support for the Chrome browser on Windows is well advanced and mostly stable. As before with Internet Explorer and Firefox the goal is to hide the browser differences and enable a single test to run unchanged on all three browsers. Not implemented at this point are various browser dialogs as well as file up- and download. Another current restriction is that only one instance of Chrome can be run by QF-Test in parallel.
bullet 
The concept of generic classes, initially available for the web engine only, has been extended to support JavaFX and soon all GUI engines. It is the basis for interoperable tests that work for different GUI engines, provides a higher level of abstraction and more flexible and robust component recognition. Recording of generic classes is configured via the option "Record generic class names for components".
See the video Dealing with the explosion of complexity in web test automation for a vivid demonstration of the explosion of complexity in AJAX user interfaces. This applies just as well to JavaFX which shares the automation problems of a UI built from a large number of small GUI elements and for which QF-Test's approach with generic classes fits perfectly.
bullet 
Tolerant class matching when recording: Existing nodes in QF-Test's component hierarchy will be reused as long as they match one of the classes of the recorded component. This means that when switching to/from generic class recording, no components will be forcibly re-recorded. This has no impact on the 'Update components' feature which always updates the respective components according to the current recording option settings.
bullet 
Connection with the SUT is now implemented via the Java agent mechanism by default. It is faster, more stable - especially for Java WebStart and Applets - and much more flexible and powerful. In case of problems the Java agent mechanism can be disabled via the option "Connect via QF-Test agent".
bullet 
During SUT startup Jython and Groovy are now loaded on demand, leading to faster and more reliable startup. Jython in particular was one of the main reasons for problems with Java WebStart. This also reduces the overhead and memory footprint if either of the languages is not used at all.
bullet 
Support was added for the AJAX framework jQuery UI.
bullet 
Eclipse/SWT support was added for the Eclipse 4.4 "Luna".
bullet 
The Nebula NatTable component is now supported by default and automatically recognized.
bullet 
Colored syntax highlighting of tree nodes was added which significantly improves readability of test-suites.
bullet 
The shared terminal now provides coloring of different message types. The new group of "Terminal options" encloses a bunch of new settings to adjust text display in the shared terminal. Font size and type can be defined as well as a number of regular expressions to highlight and/or filter arbitrary text in the output.
bullet 
It is now possible to set breakpoints on 'Component' nodes so as to enter the debugger as soon as the node gets referenced.
bullet 
For a failed 'Check items' node both run-log and report now contain a context diff of the expected and actual values so that all deviations can quickly be identified.
bullet 
Relative 'Test calls' with a leading '.' in the 'Test name' attribute are now supported.
bullet 
In places where QF-Test supports regular expressions, e.g. 'Text', 'Feature' or 'Items', normal text can now be turned into a properly quoted regular expression by right-clicking and selecting 'Escape text for regular expressions' from the context menu.
bullet 
Handling of items with multi-line text, e.g. tree nodes, table headers or cells, list items etc. has been improved.
bullet 
Search and replace operations for variables can now be limited further to cover only variable names or variable values.
bullet 
The manual chapter on integration with HP ALM - QualityCenter was rewritten from scratch.

Changes that can affect test execution:

bullet 
The 'Wait for component to appear' node implicitly waits for the respective SUT client to connect for the required GUI engine. In case the wait fails, a ComponentNotFoundException is thrown with a message that explains whether the component was not found, the respective SUT client is not connected or whether there is no matching GUI engine available for that client. The 'Expected message' attribute of a 'Catch' node can be used to differentiate between those causes.
In absence of a suitable client there was an inconsistency in older QF-Test versions, causing either a ComponentNotFoundException or a ClientNotConnectedException to be thrown, depending on whether such a client was previously connected or not. In case your test still expects a ClientNotConnectedException you either need to change the 'Catch' node, add an additional 'Catch' or prepend the 'Wait for component to appear' node with a 'Wait for client to connect' node.
bullet 
The new option "How to handle disabled components" defines what to do when a disabled 'Component' node is referenced during test execution. In previous versions of QF-Test the disabled state was ignored which sometimes led to confusion. The default now is to log an error. Consequently, disabled 'Component' nodes are no longer re-used when recording.
bullet 
There is a new option called "Default timeout for checks (ms)" that - as its name implies - defines a default timeout for checks that have no 'Timeout' attribute set. It increases general stability of check execution. If your tests include a lot of 'Check' nodes without 'Timeout' that are expected to fail, test execution time may increase. In this case you may want to set this option back to 0, the old default or, preferably, update the respective nodes and set their 'Timeout' attribute to 0.

New packages and procedures in the standard library qfs.qft

bullet 
The new qfs.fx package holds a full set of procedures for interacting with JavaFX components.
bullet 
The new qfs.utils.ssh package provides procedures for client-side ssh connections.
bullet 
There's a new check utility procedure called qfs.check.checkValueInRange.
bullet 
Various new procedures for interacting with Swing components:
qfs.swing.checkbox.deselectWithCoordinates
qfs.swing.checkbox.selectWithCoordinates
qfs.swing.checkbox.setWithCoordinates
qfs.swing.general.clickAtComponentWithDetails
qfs.swing.general.doClickWithDetails
qfs.swing.general.waitForComponent
qfs.swing.general.waitForComponentForAbsence
qfs.swing.list.clickItemWithDetails
qfs.swing.menu.selectItemWithCoordinates
qfs.swing.menu.selectSubItemWithCoordinates
qfs.swing.menu.setCheckItemWithCoordinates
qfs.swing.menu.setSubCheckItemWithCoordinates
qfs.swing.menu.selectMenuItemInHierarchyWithCoordinates
qfs.swing.menu.selectCheckMenuItemInHierarchyWithCoordinates
qfs.swing.popupmenu.clickItemWithDetails
qfs.swing.popupmenu.selectSubItemWithCoordinates
qfs.swing.popupmenu.setCheckItemWithCoordinates
qfs.swing.popupmenu.setSubCheckItemWithCoordinates
qfs.swing.radiobutton.selectWithCoordinates
qfs.swing.table.checkbox.deselectWithCoordinates
qfs.swing.table.checkbox.selectWithCoordinates
qfs.swing.table.checkbox.setWithCoordinates
qfs.swing.table.clickCellWithDetails
qfs.swing.tree.clickNodeWithDetails
qfs.swing.tree.collapseWithCoordinates
qfs.swing.tree.collapseNodeWithCoordinates
qfs.swing.tree.expandWithCoordinates
qfs.swing.tree.expandNodeWithCoordinates
qfs.swing.tree.expandNodesWithCoordinates
bullet 
Various new procedures for interacting with SWT components:
qfs.swt.checkbox.deselectWithCoordinates
qfs.swt.checkbox.selectWithCoordinates
qfs.swt.checkbox.setWithCoordinates
qfs.swt.general.clickAtComponentWithDetails
qfs.swt.general.doClickWithDetails
qfs.swt.general.waitForComponent
qfs.swt.general.waitForComponentForAbsence
qfs.swt.list.clickItemWithDetails
qfs.swt.menu.selectItemWithCoordinates
qfs.swt.menu.selectSubItemWithCoordinates
qfs.swt.menu.setCheckItemWithCoordinates
qfs.swt.menu.setSubCheckItemWithCoordinates
qfs.swt.menu.selectMenuItemInHierarchyWithCoordinates
qfs.swt.menu.selectCheckMenuItemInHierarchyWithCoordinates
qfs.swt.popupmenu.clickItemWithDetails
qfs.swt.popupmenu.selectSubItemWithCoordinates
qfs.swt.popupmenu.setCheckItemWithCoordinates
qfs.swt.popupmenu.setSubCheckItemWithCoordinates
qfs.swt.radiobutton.selectWithCoordinates
qfs.swt.table.checkbox.deselectWithCoordinates
qfs.swt.table.checkbox.selectWithCoordinates
qfs.swt.table.checkbox.setWithCoordinates
qfs.swt.table.clickCellWithDetails
qfs.swt.tree.clickNodeWithDetails
qfs.swt.tree.collapseWithCoordinates
qfs.swt.tree.collapseNodeWithCoordinates
qfs.swt.tree.expandWithCoordinates
qfs.swt.tree.expandNodeWithCoordinates
qfs.swt.tree.expandNodesWithCoordinates
bullet 
Various new procedures for interacting with web components:
qfs.web.checkbox.deselectWithCoordinates
qfs.web.checkbox.selectWithCoordinates
qfs.web.checkbox.setWithCoordinates
qfs.web.general.clickAtComponentWithDetails
qfs.web.general.doClickWithDetails
qfs.web.general.waitForComponent
qfs.web.general.waitForComponentForAbsence
qfs.web.list.clickItemWithDetails
qfs.web.radiobutton.selectWithCoordinates
qfs.web.table.clickCellWithDetails

Software that is no longer supported:

QFS is taking pains to support even very old software. QF-Test still runs, for example, under Windows XP or with an SUT based on Java 1.5 or 1.6 but for systems that are no longer supported by their own vendors we cannot provide full support.

Libraries that are required for the Firefox and Eclipse/SWT versions listed below are no longer part of the default installation of QF-Test. The majority is still being maintained, albeit with limited testing. If you need support for such a system, please get in touch with QFS via support@qfs.de.

Official support has been dropped for Java 1.5, Internet Explorer 7 and older, Firefox 25 and older (except Firefox 24 ESR) as well as Eclipse/SWT 3.7 and older.

Version 3.5.7 - July 22, 2014

New features:

bullet 
Support was added for Firefox versions 31 and 32.
bullet 
Eclipse / SWT support was added for Eclipse version 4.4 "Luna".
bullet 
The command line arguments -exitcodeignorewarning, -exitcodeignoreerror and -exitcodeignoreexception are now also available in calldaemon mode. These options are helpful for integration with continuous integration tools like Hudson/Jenkins or TeamCity as the exit code of a QF-Test batch run can be forced to 0 even in case of warnings, errors or exceptions.

Bugs fixed:

bullet 
On Linux systems like RHEL 6.5 with an old version of glibc, instrumented 64bit versions of Eclipse failed to start. This dependency on a newer version of glibc has been removed.
bullet 
For SWT QF-Test refused to replay hard events on negative coordinates which, however, are necessary to reach a window on a second monitor placed to the left of the main screen on Windows.
bullet 
The check for the editable state of INPUT:TEXT, INPUT:PASSWORD and TEXTAREA nodes was missing for web clients.
bullet 
The "All lines" check for Swing JTextArea components was not recorded correctly when clicking below the first line of text.
bullet 
When canceling an edit in the detail view or adding a new node, QF-Test now checks whether modifications were made and asks for confirmation before discarding those.
bullet 
When toggling the disabled state of the selected node, modifications made but not confirmed in the detail view were silently discarded.
bullet 
In very special cases running a test in a QF-Test daemon could fail due to a missing engine license even though the license was available.

Version 3.5.6 - April 29, 2014

New features:

bullet 
Support was added for Firefox versions 29 and 30.
bullet 
The new 'Procedure' qfs.web.browser.mozilla.cleanupProfileDir in the standard library qfs.qft attempts to remove redundant and broken files (most notably places.sqlite) in the Firefox profile directory used for testing (<user.home>/.qftest/mozProfile by default). The procedure is called automatically during the standard startup sequence via the call to qfs.web.browser.settings.doStartupSettings.

Bugs fixed:

bullet 
The warning dialog for duplicate IDs in a test-suite is no longer shown in batch mode.
bullet 
An Excel 2010 sheet with a cross-sheet reference to a pure number is now handled correctly by the 'Excel data file' node.
bullet 
In some web pages content inside an IFRAME could not automatically be scrolled to the correct location for replaying a hard mouse event or performing an image check.
bullet 
The print dialog is now shown correctly in Firefox.
bullet 
The fix for Java 8 focus handling in QF-Test version 3.5.5 could cause a very subtle issue in focus behavior for popup windows.

Patch 3.5.5-p1 - February 28, 2014

Bugs fixed:

bullet 
In a Jython SUT script, importing a Java class from the SUT could lead to the error "RuntimeError: maximum recursion depth exceeded".

Version 3.5.5 - February 25, 2014

New features:

bullet 
Support for Firefox version 27 was updated and new support added for Firefox version 28.
bullet 
Eclipse / SWT support was updated for service release 2 of Eclipse version 4.3.
bullet 
The driver test-suites and documentation for the integration with imbus TestBench were updated.
bullet 
QF-Test is now less restrictive when comparing document URLs or href attributes, so a simple change of a hostname, IP address or port no longer requires working with regular expressions in the 'Feature' attribute.

Bugs fixed:

bullet 
Focus handling for replay with Java 8 has been improved and QF-Test now works around a bug in Java 8 when setting a window topmost on Windows systems.
bullet 
Proxy settings for Internet Explorer are now application-local, so even after a crash the system proxy settings remain unchanged.
bullet 
The user agent for Internet Explorer 11 is now reported correctly by QF-Test's embedded browser.
bullet 
Firefox confirmation dialogs for closing or navigating away from a web page are now handled correctly and can be interacted with.
bullet 
Input of Unicode characters from 'Text input' nodes with 'Replay single events' set was not replayed correctly on some Linux systems.
bullet 
Closing the QF-Test main workbench with a run-log still open, then jumping from that run-log to a test-suite caused the saved session of opened test-suites to get lost.

Version 3.5.4 - December 11, 2013

New features:

bullet 
Support was added for Firefox versions 26 and 27.
bullet 
Support for the AJAX toolkit ZK was updated for ZK version 7.
bullet 
Synchronization with AJAX HTTP requests was improved for the toolkits ExtJS, ICEfaces, PrimeFaces and ZK.
bullet 
On Windows the one-time installation of the QF-Test Javascript bridge for Firefox no longer requires starting QF-Test once with administrator privileges.

Bugs fixed:

bullet 
WebStart applications are still a moving target. Various fixes for special cases were implemented to make startup of WebStart applications more reliable.
bullet 
Mouse events with variables for the X or Y coordinate that expand to empty values were not replayed to the middle of the target but to the relative coordinate 0.
bullet 
In case of deep component hierarchies QF-Test no longer logs excessive component information which, in extreme cases, could cause the SUT to run out of memory.
bullet 
A memory and thread leak in the DaemonLocator class has been plugged.
bullet 
The JNA library included in Jython no longer triggers stackguard warnings.
bullet 
An exception caused by a special kind of HTML table with no columns in the header has been fixed.

Version 3.5.3 - September 17, 2013

New features:

bullet 
Support was added for the AJAX toolkit ICEfaces.
bullet 
QF-Test can now automatically detect whether a web page is based on one of the supported AJAX toolkits and installs the respective resolver.
bullet 
Support was added for Firefox versions 24 and 25.
bullet 
The QF-Test demo video on the welcome dialog now links to the updated video on the QFS home page which is fully redesigned, including spoken explanations.
bullet 
It is now possible to copy and paste table cells back and forth between QF-Test tables and Excel or OpenOffice spreadsheets.
bullet 
When changing the name of a parameter in callable nodes like a 'Procedure' QF-Test now offers to automatically update the variable name in all calling nodes.
bullet 
The standard library qfs.qft contains several new procedures for working with standard Swing dialogs based on the JOptionPane class in the package qfs.swing.optionpane.

Bugs fixed:

bullet 
Stability of startup of WebStart based clients and compatibility with older WebStart versions was further improved.
bullet 
Canceling a long search did not work reliably and could even lead to a deadlock in some cases.
bullet 
Replace operations for the regular expression ".*" could lead to double replacements in some cases.
bullet 
The associated label for components was sometimes not determined correctly if the label was placed to the right of the component.

Version 3.5.2 - July 2, 2013

Important changes

bullet 
Handling of the security dialogs for Java WebStart and applets had to be changed again.
Security warnings are now closed implicitly before connecting to QF-Test and it is possible to permanently accept a certificate during this step. The details for this operation can be configured via the procedure qfs.swing.startup.setSecurityDialogSpec.
The default delays for WebStart and applets also changed as documented in the procedure qfs.swing.startup.setDelays.

New features:

bullet 
Eclipse / SWT support was updated for the final Eclipse version 4.3 "Kepler".
bullet 
Support was added for Firefox version 23 and updated for version 22.
bullet 
Testlink support was updated for Testlink version 1.9.7.
bullet 
'Wait for component to appear' nodes now automatically handle waiting for the respective GUI engine in addition to implicitly waiting for the SUT to connect.
bullet 
Nodes for 'Procedures' and 'Packages' marked as "@deprecated" are now crossed out in the tree view.
bullet 
The new procedure qfs.web.general.integrateFirebug in the standard library qfs.qft loads Firebug Lite into the running browser which can be very helpful when writing resolvers.
bullet 
The keyboard shortcut [Shift-Control-I] can now be used to quickly pack one or more steps into an 'If' sequence.

Bugs fixed:

bullet 
The Windows executables qftest.exe and qftestc.exe failed to read the configured Java version, memory and language from the Windows registry.
bullet 
Saving test-suites and run-logs and other IO operations are now significantly faster on slow network shares.
bullet 
When changing the currently executed node via 'Continue execution from here' in the test debugger, QF-Test is now smarter in keeping as much of the current state of execution as possible, including the previously broken case when continuing from a 'Procedure' node.
bullet 
On Linux systems Firefox would crash when terminated while a dialog was still showing.
bullet 
The recently added support for ZK and PrimeFaces was fine-tuned and fixes subtle problems with specific Trees, TreeTables and other components.
bullet 
Associated labels of Swing components, recorded as "qfs:label" extra feature, are now used for generating the 'Id' attribute. For web and SWT components this was already the case.
bullet 
In the QF-Test daemon DaemonTestRunListener instances were not unregistered correctly which could slow down daemon execution after a call like
qftest -batch -calldaemon -verbose ...
bullet 
The SUT can now implement an RMIClassLoaderSpi without interference from QF-Test's RMI communication.

Version 3.5.1 - May 15, 2013

Important changes

bullet 
The Jython version provided with QF-Test was rolled back to Jython 2.5.1 because Jython 2.5.2 caused strange but reproducible problems with some SUTs. Jython is mainly used as glue code, so stability and non-interference with the SUT are far more important than compatibility with newer Python language features and modules, so the Jython version for QF-Test will remain frozen at 2.5.1 for the foreseeable future.

New features:

bullet 
New support was added for the AJAX toolkits PrimeFaces and ZK and support for Eclipse RAP was updated to RAP version 2.0.
bullet 
Eclipse / SWT support was added for Eclipse version 4.3 "Kepler".
bullet 
Support was added for Firefox versions 21 and 22.
bullet 
The new procedure qfs.swing.filechooser.selectFiles can be used to select several files in a multi-select enabled Swing JFileChooser.
bullet 
The new 'Browser HTTP request' node can be used to replay HTTP GET or POST request directly in the running browser. In contrast to the existing 'Server HTTP request' node, which interacts directly with the server, the 'Browser HTTP request' can be combined with event and check nodes.
bullet 
HTML reports now contain pie charts to visualize the number of successful, failed and skipped tests. A click on the chart brings up a more detailed graph. The directory structure of reports has been cleaned up by moving all images and screenshots to sub-directories.
bullet 
When started from QF-Test Firefox now automatically accepts SSL certificates for HTTPS connections, limited to the current session.
bullet 
Testlink support was updated for Testlink version 1.9.4.

Bugs fixed:

bullet 
The initial connection sequence for applets and WebStart based applications had to be updated after security restraints were again tightened in recent JRE updates from Oracle. The stability of applet and WebStart startup should now be less dependent on timing and the procedure qfs.swing.dialogs.handleSecurityWarning is now able to handle all current security warnings for applets and WebStart.
bullet 
Exceptions caused by CSV or Excel files with inconsistent data are now handled cleanly.
bullet 
Updating components with 'Item' nodes could cause an exception.

Main new features in QF-Test version 3.5

Following is an overview over the main new features that have been implemented for QF-Test version 3.5. For detailed information about the differences between QF-Test 3.4 and 3.5, please see the release notes below.

bullet 
Grouping and managing test-suites in projects
bullet 
Support for AJAX toolkit Vaadin
bullet 
Better abstraction with generic classes for web pages
bullet 
Full sub-item support for several AJAX toolkits
bullet 
Secure daemon communication via SSL
bullet 
Improved component recognition without names thanks to associated label
bullet 
Integration with test management tool QMetry
bullet 
Several extensions to the standard library qfs.qft
bullet 
Jython updated to version 2.5.2
bullet 
Groovy updated to version 2.1.0

Version 3.5.0 - March 20, 2013

New features:

bullet 
Support was added for Firefox version 20.
bullet 
Eclipse / SWT support was updated for Eclipse versions 4.2.2 and 3.8.2.
bullet 
Groovy was updated to version 2.1.0.
bullet 
Explicit references between test-suites belonging to the same project are now resolved automatically provided that those test-suites have been saved with QF-Test version 3.5.0 or higher.
bullet 
Multi-line values can now be edited directly in QF-Test's table cells.
bullet 
Extra mouse buttons can now be used to move backwards/forwards between recently selected nodes.
bullet 
Double-clicking on nodes that reference other nodes now navigates to the target, e.g. from 'Procedure call' to 'Procedure'.
bullet 
Test-suite and run-log files can now be dragged onto QF-Test's main window to open them.
bullet 
The new procedure qfs.swing.dialogs.handleSecurityWarning in the standard library qfs.qft closes the security dialogs displayed by current JREs during startup of applets or WebStart based applications.
bullet 
The procedure qfs.web.browser.general.startAsNewProcess was updated to include security dialog handling.
bullet 
Another new procedure named qfs.swing.startup.startWebstartSUT can be used to run WebStart and connect to the SUT, also handling the security dialog automatically.
bullet 
The new procedure qfs.utils.files.readExcelFile can be used to read data from an excel sheet into Jython or QF-Test variables.
bullet 
The 'Server HTTP request' node now offers an optional timeout and can return the HTTP status code. Parameters are now encoded during replay instead of recording, making it easier to specify values manually. Older test-suites are converted automatically during loading to reflect this change.
bullet 
The default names recorded for GEF items are now more meaningful and result in improved recognition.
bullet 
QF-Test now integrates with the test management tool Klaros.
bullet 
The error list for a run-log now includes a timestamp column and shows information about expected errors.
bullet 
When pausing a batch test via [Alt-F12], input to the SUT is no longer blocked.
bullet 
If the new command line argument -dontkillprocesses is specified in batch mode, QF-Test will not explicitly terminate processes started as part of the tests.

Bugs fixed:

bullet 
A memory leak in case of large projects with many test-suites and complex includes has been plugged.
bullet 
A workaround has been implemented for a bug in recent JRE security updates that could cause batch tests to simply stop in the middle of execution.
bullet 
Variables could accidently be removed from component IDs when fixing references automatically.
bullet 
In special cases externalized run-logs could be missing from run-logs saved as .qzp.
bullet 
When opening an externalized log on its own, split logs contained therein could not be accessed correctly.
bullet 
A race condition during automatic project refresh could mess up the project tree view.
bullet 
The native file chooser for Windows is now implemented based on SWT instead of XFileDialog. This fixes issues when opening directories and when changing the file filter during "Save as..." operations.
bullet 
In batch execution of multiple test-suites, global variables and resources are no longer cleared before the execution of each test-suite unless the new command line argument -clearglobals is specified.
bullet 
Firefox on Linux no longer crashes on shutdown.
bullet 
For some MIME types downloading files did not work correctly with Firefox.
bullet 
Checks for the enabled state could fail in Internet Explorer if the state was set via Javascript.
bullet 
Waiting for the absence of an element could fail if the element just became invisible instead of being removed completely.
bullet 
Variables in 'Data binder' nodes are now expanded immediately during execution of the containing 'Data driver' node so that local variables bound in the 'Data driver' are evaluated correctly.
bullet 
A 'Return' in a 'Finally' node could hide an exception thrown in the containing 'Try' node.
bullet 
Using Java 7 on Mac systems could cause an exception during startup of QF-Test.
bullet 
In case a process simply refuses to be killed, the 'Stop client' node did not remove the process from the »Clients« menu, thus preventing starting a new process under the same name.
bullet 
Image checks based on algorithms were not always shown correctly in the report.
bullet 
In case dependency resolution fails due to an exception during setup even after unwinding the complete dependency stack for error escalation, QF-Test now cleans up after the final attempt so that the next test-case starts with a clean slate.
bullet 
Changes to the location of the search dialog and other dialogs were often ignored instead of automatically saved to the user preferences.

Version 3.5M3 - January 8, 2013

New features:

bullet 
Support was updated for Firefox versions 18 and 19.
bullet 
The project concept now includes support for sub-projects.
bullet 
Javascript error filters defined in the option "Errors that should be ignored" are now applied to the complete message including the URL and line number of the source of the error.
bullet 
Several checks were added for Eclipse JFace components like FormText, Link or Hyperlink.

Bugs fixed:

bullet 
The responsiveness of QF-Test severely suffered when opening many test-suites.
bullet 
Refresh of large projects on slow filesystems like Windows network shares is now significantly faster.
bullet 
If several projects were opened, automatic refresh of the project hierarchy could mess up the project tree.
bullet 
Geometry of events relative to an SWT Shell now includes the window title and borders.
bullet 
Highlighting widgets inside CTabFolders in Eclipse 4.2 now uses the correct offset.
bullet 
Errors happening outside a test-case were not listed correctly in the report if the containing test-set contained several test-cases.
bullet 
Downloading files with Firefox could cause a Javascript error if the file mimeTypes.rdf was missing from QF-Test's Mozilla profile. This file is now created on the fly if necessary.
bullet 
Closing the browser window of Internet Explorer 10 could cause the browser to deadlock instead of terminate.
bullet 
QF-Test's embedding of Internet Explorer 10 caused the browser to run in IE9 mode. Now it starts up in IE10 mode by default with the usual settings for compatibility mode enabled.
bullet 
Replaying [Tab] keystrokes on Firefox did not always trigger the correct focus traversal.
bullet 
Conflicts caused by an SUT using a Groovy 2 version other than the version provided with QF-Test are now resolved.

Version 3.5M2 - November 16, 2012

New features:

bullet 
Eclipse / SWT support was updated for Eclipse versions 4.2.1 and 3.8.1.
bullet 
Daemon communication is now secured via SSL. Manual chapter 40 explains how to increase security by creating an individual keystore or how to disable this feature in case you need daemon interaction with older QF-Test versions.
bullet 
QF-Test generated JUnit reports now contain <skipped> tags, enabling build tools like Hudson/Jenkins to correctly report skipped tests.

Bugs fixed:

bullet 
License usage for idle QF-Test daemons was not determined correctly.
bullet 
Replaying certain events in batch mode could switch QF-Test into recording mode, causing weird problems and significant loss of performance.
bullet 
Timing for startup of Java WebStart based SUTs has been further improved to significantly increase the stability of this setup.
bullet 
Some focus transitions were not triggered correctly when replaying events in a browser.
bullet 
The filename shown in a download dialog was not always correct.
bullet 
Downloads in a Vaadin based SUT could cause an exception.
bullet 
Internet Explorer 10 now reports the correct version information.
bullet 
Recording of drag and drop operations on CTabFolders in Eclipse 4.2 was broken.
bullet 
In some cases the height of SWT List items was not calculated correctly, leading to the wrong item being addressed in case of large lists with many items.
bullet 
The new 'Extra feature' attribute qfs:label was sometimes not determined correctly in the presence of Swing JSlitPane or SWT SashForm components.
bullet 
Handling of an SUT with combined SWT/AWT GUI was broken. Due to an error introduced in version 3.4.11 QF-Test was treating this as two SUT clients instead of one client with two GUI engines.

Version 3.5M1 - October 29, 2012

New features:

bullet 
With the introduction of projects, large sets of test-suites become much more manageable and updating reverse includes is now mostly a thing of the past.
bullet 
The increasingly popular AJAX toolkit Vaadin is now fully supported.
bullet 
The integration of QF-Test with various AJAX toolkits has been brought to a new level. Generic classes provide a unified view that abstracts from the technical details, focusing on typical UI elements like Tree or Table that users are familiar with. This even includes the concept of sub-items so that addressing table cells or tree nodes is now just as easy as with Swing or SWT. This level of support is currently available for Ext JS 4, RAP, RichFaces and Vaadin.
bullet 
Support was added for Firefox version 18.
bullet 
For SUTs where only few components are named - if any - component recognition has been improved by adding a new 'Extra feature' called qfs:label. It represents a best match for a label, based on various algorithms including a search for the nearest label for components that don't have one of their own. Classical forms consisting of text fields with labels next to them benefit most from it.
bullet 
Handling the opposite case, where the same component name is assigned to more than one component, is now also handled via via the new option "Validate component recognition during recording".
bullet 
QF-Test now integrates with the test management tool QMetry.
bullet 
Components in QF-Test's detail view are now sized dynamically depending on the contained data. Combined with improved scrolling this vastly improves creating and maintaining test-suites.
bullet 
The menu item »Replay«-»Reset all« can be used to stop the test, reset dependencies and global variables and kill all clients with a single action.
bullet 
On Windows QF-Test now uses the native file chooser by default, configurable via the option "Use native file chooser on Windows systems".
bullet 
There are new operations to search for various kinds of duplicates, empty tests or illegal characters. The result dialogs for these and similar operations as well as searches have more options and exported results can now be read back.
bullet 
Search and replace operations now cover whole projects and can be interrupted in case they take too long.
bullet 
Tables holding variable definitions or parameter lists can now be sorted.
bullet 
It is now possible to navigate from a component id specified in a variable table directly to the component by right-clicking the respective table cell.
bullet 
Parameters of procedures can now be added to or removed from the variable definitions of all callers via the context menu of the parameter table.
bullet 
Recording procedures for windows with many components now works significantly faster.
bullet 
Whitespace at the beginning or end of variable names is now generally removed to avoid confusion.
bullet 
There is a new hotkey (configurable via "Hotkey for recording", default [F11]) to start and stop recording directly in the SUT. The previous default binding for [F11], component recording, has been moved to [Shift-F11].
bullet 
There's a new kind of check for tree nodes that can handle whole (sub-)hierarchies at once, including indentation.
bullet 
Highlighting components in the SUT for event nodes now works even if the 'Component' node for the event is not located in the same test-suite.
bullet 
Killing the SUT and other processes now works much faster.
bullet 
Leading and trailing whitespace in 'Feature' attributes is now generally ignored. This implementation is fully backwards compatible, so it doesn't hurt if features were recorded with whitespace before.
bullet 
Line numbers are now displayed for tables where this is useful, for example in 'Data table' or 'Check items' nodes.
bullet 
In places where accidentally inserted TAB or line-break characters can do harm, most notably in variable definitions or checks, they are now represented as graphical symbols. This can be turned off via the option "Show symbols for tabulator and linebreaks".

New packages and procedures in the standard library qfs.qft:

bullet 
The new qfs.autoscreen package holds procedures for locating and interacting with components on the screen based on some previously captured image.
bullet 
Several new utility procedures:
qfs.utils.files.compareFiles
qfs.utils.variables.deleteGlobalVariablesExcept
qfs.utils.variables.deletePropertyGroup
qfs.utils.variables.deleteOnePropertyVariable
qfs.utils.variables.listAllMembersOfPropertyGroup
qfs.utils.xml.loadPropertiesFromXML
qfs.utils.sleep
bullet 
Various new procedures for interacting with Swing components:
qfs.swing.checkbox.getValue
qfs.swing.combobox.getIndexOfItem
qfs.swing.combobox.getValue
qfs.swing.combobox.getValueOfItem
qfs.swing.general.doSelect
qfs.swing.menu.selectMenuItemInHierarchy
qfs.swing.menu.selectCheckMenuItemInHierarchy
qfs.swing.radiobutton
qfs.swing.radiobutton.getValue
qfs.swing.radiobutton.select
qfs.swing.tabbedpane.getIndexOfTab
qfs.swing.tabbedpane.getValueOfTab
qfs.swing.text.getText
bullet 
Various new procedures for interacting with SWT components:
qfs.swt.checkbox.getValue
qfs.swt.combo.getIndexOfItem
qfs.swt.combo.getValue
qfs.swt.combo.getValueOfItem
qfs.swt.general.doSelect
qfs.swt.list.getIndexOfItem
qfs.swt.menu.selectMenuItemInHierarchy
qfs.swt.menu.selectCheckMenuItemInHierarchy
qfs.swt.radiobutton
qfs.swt.radiobutton.getValue
qfs.swt.radiobutton.select
qfs.swt.table.getIndexOfColumn
qfs.swt.table.getRowIndexOfCell
qfs.swt.tabfolder.getIndexOfTab
qfs.swt.tabfolder.getValueOfTab
qfs.swt.text.getText
qfs.swt.tree.multicolumn
qfs.swt.tree.multicolumn.getRowIndexByCellText
qfs.swt.tree.getIndexOfNode
bullet 
Various new procedures for interacting with web components:
qfs.web.checkbox.getValue
qfs.web.radiobutton
qfs.web.radiobutton.getValue
qfs.web.radiobutton.select
qfs.web.select
qfs.web.select.getItemCount
qfs.web.select.getIndexOfItem
qfs.web.select.getValueOfItem
qfs.web.select.getValue
qfs.web.select.selectValue
qfs.web.table
qfs.web.table.checks
qfs.web.table.checks.checkNumberOfRows
qfs.web.table.checks.checkNumberOfColums
qfs.web.table.recording
qfs.web.table.recording.activateItemRecording
qfs.web.table.recording.deactivateItemRecording
qfs.web.table.getColumnCount
qfs.web.table.getIndexOfColumn
qfs.web.table.getNameOfColumn
qfs.web.table.getRowCount
qfs.web.table.getRowIndexOfCell
qfs.web.table.getValueOfCell
qfs.web.table.selectCell
qfs.web.text.getText
bullet 
More web utilities, specifically qfs.web.ajax.uninstallToolkitResolver, the new package qfs.web.checks.style with several procedures for checking CSS style attributes of DOM nodes and a complete rewrite of qfs.web.browser.general.startAsNewProcess.

Bugs fixed:

bullet 
The modified connection mechanism still crashed Java WebStart on some occasions and has been further fine-tuned to prevent that.
bullet 
The option settings for "Errors that should be ignored" were not saved to the system configuration file.

Version 3.4.14 - March 20, 2013

New features:

bullet 
Support was added for Firefox version 20.
bullet 
Eclipse / SWT support was updated for Eclipse versions 4.2.2 and 3.8.2.
bullet 
The new procedure qfs.swing.dialogs.handleSecurityWarning in the standard library qfs.qft closes the security dialogs displayed by current JREs during startup of applets or WebStart based applications.
bullet 
The procedure qfs.web.browser.general.startAsNewProcess was updated to include security dialog handling.
bullet 
Another new procedure named qfs.swing.startup.startWebstartSUT can be used to run WebStart and connect to the SUT, also handling the security dialog automatically.

Bugs fixed:

bullet 
A workaround has been implemented for a bug in recent JRE security updates that could cause batch tests to simply stop in the middle of execution.
bullet 
Firefox on Linux no longer crashes on shutdown.
bullet 
For some MIME types downloading files did not work correctly with Firefox.
bullet 
Checks for the enabled state could fail in Internet Explorer if the state was set via Javascript.
bullet 
Waiting for the absence of an element could fail if the element just became invisible instead of being removed completely.
bullet 
A 'Return' in a 'Finally' node could hide an exception thrown in the containing 'Try' node.
bullet 
Using Java 7 on Mac systems could cause an exception during startup of QF-Test.
bullet 
Changes to the location of the search dialog and other dialogs were often ignored instead of automatically saved to the user preferences.

Version 3.4.13 - January 8, 2013

New features:

bullet 
Support was updated for Firefox versions 18 and 19.
bullet 
Javascript error filters defined in the option "Errors that should be ignored" are now applied to the complete message including the URL and line number of the source of the error.

Bugs fixed:

bullet 
The responsiveness of QF-Test severely suffered when opening many test-suites.
bullet 
Geometry of events relative to an SWT Shell now includes the window title and borders.
bullet 
Highlighting widgets inside CTabFolders in Eclipse 4.2 now uses the correct offset.
bullet 
Errors happening outside a test-case were not listed correctly in the report if the containing test-set contained several test-cases.
bullet 
Downloading files with Firefox could cause a Javascript error if the file mimeTypes.rdf was missing from QF-Test's Mozilla profile. This file is now created on the fly if necessary.
bullet 
Closing the browser window of Internet Explorer 10 could cause the browser to deadlock instead of terminate.
bullet 
QF-Test's embedding of Internet Explorer 10 caused the browser to run in IE9 mode. Now it start up in IE10 mode by default with the usual settings for compatibility mode enabled.
bullet 
Replaying [Tab] keystrokes on Firefox did not always trigger the correct focus traversal.

Version 3.4.12 - November 16, 2012

New features:

bullet 
Eclipse / SWT support was updated for Eclipse versions 4.2.1 and 3.8.1.
bullet 
Support was added for Firefox version 18.

Bugs fixed:

bullet 
The modified connection mechanism still crashed Java WebStart on some occasions and has been further fine-tuned to prevent that.
bullet 
The option settings for "Errors that should be ignored" were not saved to the system configuration file.
bullet 
Some focus transitions were not triggered correctly when replaying events in a browser.
bullet 
The filename shown in a download dialog was not always correct.
bullet 
Internet Explorer 10 now reports the correct version information.
bullet 
Recording of drag and drop operations on CTabFolders in Eclipse 4.2 was broken.
bullet 
In some cases the height of SWT List items was not calculated correctly, leading to the wrong item being addressed in case of large lists with many items.
bullet 
Handling of an SUT with a combined SWT/AWT GUI was broken. Due to an error introduced in version 3.4.11 QF-Test was treating this as two SUT clients instead of one client with two GUI engines.

Version 3.4.11 - October 4, 2012

New features:

bullet 
QF-Test is now compatible with Java applets running on JRE version 1.6.0_35 or higher or JRE version 1.7.0_7 or higher. A security fix from Oracle broke the existing applet connection mechanism. The new mechanism should also improve stability of Java WebStart based SUTs.
bullet 
Support was added for Firefox version 17.
bullet 
Via the new option "Errors that should be ignored" it is now possible to ignore specific Javascript error messages while still treating others as an error.
bullet 
When copying multiple lines of a table in the detail view of QF-Test these are now also copied to the system clipboard as a list of TAB-separated values, thus enabling pasting into a spreadsheet.
bullet 
The new procedure qfs.utils.logNativeMemory in the standard library qfs.qft can be used to get information about the native memory use of an SUT client.
bullet 
Windows executables and installers created by QFS are now signed with an official certificate for smoother integration with Windows 7 and Windows 8.

Bugs fixed:

bullet 
Downloads of large files were sometimes truncated.
bullet 
The new <INPUT> types in HTML 5 are now mapped to INPUT:TEXT so that tests remain independent of whether the browser supports them.
bullet 
The command line argument -runlogdir <directory> now also works for daemon calls via qftest -batch -calldaemon.
bullet 
Empty formatted cells in an Excel 2010 sheet are now handled correctly by the 'Excel data file' node.
bullet 
Toolbar icons for QF-Test's browser wrapper are now transparent and no longer look horrible on Windows 7.

Patch 3.4.10-p1 - August 8, 2012

Bugs fixed:

bullet 
Fixed a race condition in the new suite IO optimization that could lead to an exception in rare cases.

Version 3.4.10 - August 7, 2012

New features:

bullet 
Support was added for Firefox versions 15 and 16.
bullet 
The performance of complex QF-Test operations like finding references has been significantly improved for large projects on slow filesystems like network shares.

Bugs fixed:

bullet 
Crashes of IE and Firefox were further reduced.

Version 3.4.9 - June 29, 2012

New features:

bullet 
Eclipse / SWT support was added for Eclipse "Juno" versions 4.2 and 3.8.
bullet 
Support was added for Firefox version 14.
bullet 
Several new transformation options for nodes in the test-suite were introduced.

Bugs fixed:

bullet 
A significant memory leak in QF-Test's browser wrapper was plugged.
bullet 
Several causes for browser crashes were fixed, both for Internet Explorer and Firefox.
bullet 
Component recognition now also works correctly with components recorded in a flat hierarchy, even if the web page contains <FRAME> nodes.
bullet 
The progress bar in Internet Explorer always remained visible even when a page was completely loaded.
bullet 
If the path for the Firefox installation directory contained special characters, Firefox could not be started correctly from QF-Test.
bullet 
On Windows, popup menus in an Eclipse / SWT application were sometimes mistakenly considered to be invisible.
bullet 
Files are no longer overwritten without asking when an image is saved from a 'Check image' node.
bullet 
'Component group' and 'Window group' nodes are now handled and integrated correctly when importing components from a test-suite.
bullet 
Another special case for escaping '$' characters in component names has been fixed.

Version 3.4.8 - June 5, 2012

New features:

bullet 
Support was added for the current Firefox version 13.
bullet 
Eclipse / SWT support was added for Eclipse versions 3.8M7 through 3.8RC2 and experimental support for Eclipse version 4.2M7 through 4.2RC2.
bullet 
Support for the Richfaces toolkit was improved.
bullet 
The 'Excel data file' node now also handles Excel files with the '.xlsm' extension.

Bugs fixed:

bullet 
Escaping of '$' characters in component names was broken in the component and procedure recorder.
bullet 
Enabled checks did not work correctly with Internet Explorer 9 running in IE 7 compatibility mode.
bullet 
Firefox could crash when closing a browser window.
bullet 
When recording procedures the calls for <SELECT> elements were created incorrectly.

Version 3.4.7 - April 24, 2012

New features:

bullet 
Support was added for the current Firefox version 12.
bullet 
The new 'Procedure' qfs.swt.ctabfolder.openViewMenu can be used to generically open the ViewMenu of a CTabFolder based on the tab name, both for Eclipse 3.x and Eclipse 4.

Bugs fixed:

bullet 
Script errors were not formatted correctly when shown in the error dialog. In the run-log those errors were shown correctly.
bullet 
Excel 2010 files used in a data driver with an 'Excel data file' node were not closed correctly.
bullet 
There's a new workaround for the workaround for the missing MSVC manifest in a DLL from Firefox 10 and higher. Problems with another missing MSVC DLL on Windows XP and deadlocks when loading a Flash component in Firefox on Windows have been fixed.

Version 3.4.6 - March 27, 2012

New features:

bullet 
Eclipse / SWT support was added for Eclipse versions 3.7.2 and 3.8M6 and experimental support for Eclipse version 4.2M6.
bullet 
The 'Procedures' qfs.swt.ctabfolder.closeTab and qfs.swt.ctabfolder.checkTabIsDirty now also support Eclipse 4.

Bugs fixed:

bullet 
The fix for SUTs that use RMI with a custom implementation of the Service Provider Interface (SPI) could cause a subtle class loading problem that has been fixed.
bullet 
Deleting the last row in a variable table in QF-Test could lead to an exception when subsequently trying to move a table row.
bullet 
QF-Test's handling of Javascript errors could cause Internet Explorer to crash.
bullet 
If QF-Test was accidently started with the bin directory of an older QF-Test version as its working directory, starting a browser on Windows could fail due to conflicts between DLL versions.
bullet 
Use of a special API in Internet Explorer can lead to very subtle deviations in Javascript execution. QF-Test no longer uses this interface.
bullet 
On some systems the workaround for the missing MSVC manifest in a DLL from Firefox 10 and higher could cause a problem with another DLL and prevent QF-Test from starting Firefox.

Version 3.4.5 - March 12, 2012

New features:

bullet 
Support was added for the current Firefox version 11.
bullet 
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:

bullet 
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.
bullet 
Cancelling a long search in a large test-suite did not work reliably.
bullet 
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.
bullet 
The QF-Test daemon was not registered at the default port when started without the argument -daemonport <port>.
bullet 
SUTs that use RMI with a custom implementation of the Service Provider Interface (SPI) failed to connect to QF-Test.
bullet 
The combination of running 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.
bullet 
QF-Test now works around a problem with a missing MSVC manifest in Firefox 10, causing an error message about incorrect loading of the C runtime library.
bullet 
Firefox 10 crashed when navigating to about:plugins.
bullet 
A download triggered at Javascript level via a link starting with '#' caused the browser window to close.

Version 3.4.4 - January 30, 2012

New features:

bullet 
Support was added for current versions of Firefox 9 and 10.
bullet 
Eclipse / SWT support was added for Eclipse version 3.8M5 and experimental support for Eclipse version 4.2M5.
bullet 
New checks were introduced for SWT Decorations, small icons typically shown next to a text field. You can now check the visibility, icon and tool tip of a Decoration.
bullet 
Iteration ranges can now also be used when setting up data at script level via the databinder module or by calling one of the 'Procedures' qfs.databinder.bindList or qfs.databinder.bindSets in the standard library qfs.qft.
bullet 
The thumbnail images shown for screenshots in the HTML report are now of higher quality.

Bugs fixed:

bullet 
A small change in QF-Test version 3.4.3 regarding the RMI communication between QF-Test and the SUT was undone because of possible side-effects when the SUT was using RMI itself.
bullet 
When using 'Check image' nodes with an advanced algorithm and a timeout QF-Test always used up the full timeout even when the image matched immediately.
bullet 
When a 'Check' node with a timeout fails, QF-Test used to show the initial state of the target component in the run-log. Now it shows the state at the end of the timeout period instead.
bullet 
When using Drag&Drop to move nodes within QF-Test the tree could jump erratically in some cases.
bullet 
Trying to remove the same node twice from a search result dialog could lead to an exception.
bullet 
In the standard test-suite library qfs.qft the 'Procedure' qfs.shellutils.touch now correctly updates the timestamp for existing files and the 'Procedure' qfs.autowin.getURLFromIE now also works with Internet Explorer version 6.
bullet 
When recording a mouse click on an SWT ToolItem that opens a drop down menu QF-Test now records the coordinates so the event can replay correctly.
bullet 
If an alert dialog was shown after closing a modal browser window, the main browser window could remain blocked after closing the alert.
bullet 
Javascript errors in Internet Explorer were not logged correctly in QF-Test's run-log.
bullet 
In some cases the initial loading of a web page did not succeed.
bullet 
Highlighting the selected component in a browser on Linux has been improved.
bullet 
Web pages with a Flash element were sometimes not displayed correctly on Linux.
bullet 
The name recorded for file upload on Linux contained the Windows file separator character '\'
bullet 
There were problems with browser startup on special Windows versions if QF-Test was installed below a directory with blanks in its name, e.g. "C:\Program Files (x86)"

Version 3.4.3 - October 27, 2011

New features:

bullet 
Support was added for current versions of Firefox 8 and 9.
bullet 
The 'Excel data file' node now supports reading .xslx files in Excel 2010 format.
bullet 
The performance of some advanced image check algorithms was significantly improved.
bullet 
It is now possible to fetch option values in a script via the new method rc.getOption.

Bugs fixed:

bullet 
When switching test-suites by clicking a suite tab the keyboard focus was not correctly restored.
bullet 
The keyboard shortcut [Ctrl-D] for setting a bookmark did not work.
bullet 
Jumping from a node in the debugger window to the same node in the test-suite now works again.
bullet 
In some special cases QF-Test could kill the wrong process on Windows when trying to terminate the SUT.

Version 3.4.2 - September 15, 2011

New features:

bullet 
Full support was added for Firefox 6 and experimental support for Firefox 7.
bullet 
For easier integration with continuous integration tools like Hudson/Jenkins or TeamCity the exit code of a batch run can be forced to 0 even in case of warnings, errors or exceptions with the help of the command line arguments -exitcodeignorewarning, -exitcodeignoreerror and -exitcodeignoreexception.
bullet 
If the option "Replace no-break space with normal space" is activated, QF-Test now represents no-break space characters in a web page as normal space characters in checks and 'Component' node attributes to avoid confusion.
bullet 
QF-Test now supports capture and replay of "expand" and "collapse" events for SWT ExpandItems.

Bugs fixed:

bullet 
The integrated help viewer of Eclipse uses a separate SWT Display on Windows which caused problems during replay. It is now consistently represented with 'GUI engine' "swt1".
bullet 
Direct execution of Javascript code now also works in Internet Explorer 9 despite stronger security restrictions.
bullet 
The AJAX resolver for GWT has been updated to version 1.4.0 to fix filtering of <DIV> nodes from the component hierarchy.
bullet 
Opening a modal popup window could crash Firefox 6 on Windows.
bullet 
Double clicks are now recorded correctly in Internet Explorer.
bullet 
A 'Fetch text' node for a <SELECT> node now retrieves the text of the selected <OPTION> node and 'Fetch text' nodes for <OPTION> elements represented as items are working correctly.
bullet 
Printing unicode strings in Jython could cause problems when running in batch mode.
bullet 
The content of 'Data table' nodes was missing in the run-log.
bullet 
A 'Wait for client to connect' node with a very short timeout did not throw a ClientNotConnectedException when single-stepping in the debugger.
bullet 
The QF-Test daemon was leaking threads when starting a remote SUT process for use with the procedure qfs.daemon.startRemoteSUT.
bullet 
When updating failed image checks from the run-log the size of the image was not always updated correctly.
bullet 
When recording procedures, QF-Test failed to create a procedure in case the respective component had no value for a placeholder like <COMPFEATURE>.

Version 3.4.1 - July 15, 2011

New features:

bullet 
Full support was added for Firefox 5 and experimental support for Firefox 6.
bullet 
Eclipse / SWT support was updated for Eclipse version 3.7 Indigo.
bullet 
Groovy was updated to version 1.7.10.
bullet 
Error messages for errors in Groovy scripts now show proper context and line numbers.
bullet 
QF-Test can now handle custom SWT components that hide their child Widgets by overriding getChildren() to return an empty array.
bullet 
Support was added for ExtJS version 4 and for RichFaces version 4.
bullet 
The 'As regexp' attribute of 'Window' and 'Component' nodes can now be defined as a variable value.
bullet 
The startup sequence created by the quickstart wizard for web applications now has a smarter layout and is easier to adjust.
bullet 
On Windows systems QF-Test now makes use of the always-on-top attribute to force SUT windows to the front even if normally prevented by Windows. To disable this feature, deactivate the option 'When raising windows, try to force them to the top'.
bullet 
A new check was added to directly check the icon of a component instead of having to capture the whole component and define a check region.

Bugs fixed:

bullet 
When loading the test-suites to restore the last session upon startup, QF-Test did not check for auto-save files.
bullet 
It was possible to start parallel tests in the same context by hitting [Return] at the right time. This could lead to confusing results in the run-log and even to exceptions.
bullet 
Swing applications started via Java WebStart have two independent application contexts, a user context and a security context. Unless the 'GUI engine' attribute of a 'SUT script' node explicitely defines the engine, the script is now always correctly executed in the user context and not in the security context.
bullet 
Special support for JSlider components was missing.
bullet 
The special variable ${qftest:runid} did not expand to the correct value if the runid was specified explicitly via -runid <id> in batch mode.
bullet 
A forced download triggered via a special PHP construct could cause Internet Explorer to crash.
bullet 
Clearing the cache for Firefox did not always work correctly.
bullet 
Trying to record a check for an XML document displayed in Internet Explorer could crash the browser.
bullet 
It is now possible to record checks for applets even when they are embedded in QF-Test's browser wrapper.
bullet 
The Groovy implementation of qf.logError was broken.
bullet 
In a workbench view with many open test-suites and some test-suite tabs scrolled out to the left, coordinates for dragging test-suite or node to different test-suites were off, leading to surprising results.
bullet 
QF-Test was leaking resources when taking Screenshots in an Eclipse / SWT SUT.
bullet 
Calling Display.asyncExec from a timer could crash Eclipse on Linux Gtk with 64bit.
bullet 
The order of SWT.Activation events could show very subtle differences between manual replay and automatic replay with soft events.
bullet 
A very long search string could mess up the size of the search and replace dialog.
bullet 
Markers in run-logs did not propagate beyond 'External log' nodes.
bullet 
Fallback to lazy binding did not work for not-yet-bound properties.

Main new features in QF-Test version 3.4

Following is an overview over the main new features that have been implemented for QF-Test version 3.4. For detailed information about the differences between QF-Test 3.2 and 3.4, please see the release notes below.

bullet 
Jython updated to version 2.5.1
bullet 
Groovy updated to version 1.7.6
bullet 
Support for Eclipse / SWT 3.6.2 and 3.7
bullet 
Web testing support for Firefox 4 and 5 as well as Internet Explorer 9
bullet 
Integration with Continuous Integration tool Hudson/Jenkins
bullet 
Fault-tolerant image checks
bullet 
Advanced search and replace
bullet 
Iteration ranges for data drivers
bullet 
Direct interaction with web servers
bullet 
Extended import functionality
bullet 
Debugger integrated into the workbench
bullet 
Ability to create a test-suite from a run-log
bullet 
Automatic splitting of run-logs and graceful handling of OutOfMemoryErrors
bullet 
Improved backwards/forwards navigation
bullet 
Improved pkgdoc and testdoc documentation
bullet 
Improved coordinate abstraction for mouse events
bullet 
Variables with default values and many additional special variables

Patch 3.4.0-p1 - June 27, 2011

New features:

bullet 
Support was added for Firefox version 5 and Eclipse / SWT version 3.7 Indigo.

Version 3.4.0 - May 26, 2011

New features:

bullet 
Support for testing Eclipse / SWT version 3.7 was updated.
bullet 
All 'Data binder' nodes now have an attribute named 'Iteration ranges' that can be used to limit the iteration to a single element or one or more intervals, which is very convenient when implementing tests, continuing a test that had to be stopped or performing a retest with a limited subset.
bullet 
In workbench mode the current session with the currently open test-suites and the positions therein is now saved when QF-Test is closed and restored upon startup, provided the option "Restore last session on startup" is active. Also added to the workbench view were the ability to save all modified test-suites via the »File« menu and switching between recently active test-suites via [Control-F6].
bullet 
Moving backwards/forwards between selected nodes has been unified and should now work consistently even for special cases. After recording components you can jump directly to the recorded node by moving forwards, even if no node was actually recorded and the existing node is in a different test-suite.
bullet 
Filter capabilites were added to the search/replace result and other multi result dialogs.
bullet 
Marks can now also be set for nodes in a run-log, so multi-step search operations are now also available in run-logs.
bullet 
The quickstart wizard has improved support for launching applets in a browser and for setting the compatibility mode in internet explorer, backed by the procedures qfs.web.browser.general.startAsNewProcess and qfs.web.browser.settings.enableCompatibilityMode in the standard library qfs.qft.
bullet 
When started in batch mode with the command line argument -verbose [<level>], QF-Test now displays exception, error and warning counts for each 'Test-case'.
bullet 
The new package qfs.autowin.acrobat in the standard library qfs.qft contains methods to save a PDF document showing in an Acrobat window or to copy its text content to a file via the clipboard (Windows only). These are complemented by the qfs.utils.files package with procedures to verify the content of a text file.
bullet 
The new methods setProperty and getProperty in the generic scripting module qf can be used to associate arbitrary data with a GUI element, e.g. to cache some resolved feature or name values or other information that is too expensive to compute every time a resolver method is called.
bullet 
The TestRunListener API has been extended to provide the number of exceptions, errors and warnings that occurred below a given node in the TestRunEvent of a call to nodeExited.
bullet 
The AJAX resolver for GWT has been updated to version 1.2.0. It now filters irrelevant <DIV> nodes from the component hierarchy and has improved support for obfuscated GWT class names.

Bugs fixed:

bullet 
Early checking to handle OutOfMemoryErrors more gracefully could impact test execution speed significantly with JDK 1.5 on Windows. Tests should now run at full speed again with all JDK versions.
bullet 
Some of the advanced image check algorithms did not work correctly with JDK 1.5. All algorithms are now fully supported for JDK 1.5 and higher and return consistent results, independent of the JDK version, except for resizing, which is implemented differently in the various JDK versions and can lead to minor deviations in the resulting probability.
bullet 
The procedure qfs.shellutils.copy in the standard library qfs.qft was broken. It now copies files and directories correctly, recursively if necessary and handles special cases like copying a directory into itself.
bullet 
'Check image' nodes now work correctly in Firefox 4.0.
bullet 
Scrolling an element visible was not always possible in IE9 and some special cases with a deeply nested hierarchy.
bullet 
In IE9 nodes were not highlighted properly and highlighting could interfere with recording image checks.
bullet 
Browser settings for IE9 did not always take effect.
bullet 
A download operation triggered from a popup window could crash the browser.
bullet 
A running test in the QF-Test daemon can now be interrupted and stopped cleanly via -stoprun even if the test is currently waiting for something.
bullet 
The structure of the JUnit XML report is now compatible with Atlassian Confluence.
bullet 
In Groovy the method rc.getProperties() was not implemented correctly.

Version 3.4M2 - March 10, 2011

New features:

bullet 
Support was added for testing Eclipse / SWT versions 3.6.2 and 3.7 Milestone 5.
bullet 
The search and replace dialogs are now integrated so it is possible to start with a search and continue replacing, based on the same criteria. Also, the replace dialog is no longer modal so it can be kept open while editing.
bullet 
Integration of the debugger functionality into the workbench view is now complete. The current variable bindings are displayed automatically whenever the debugger is entered unless the option "Show variable bindings automatically" is turned off.
bullet 
The keyboard shortcuts [Alt-1] through [Alt-9] navigate directly to the respective test-suite tabs in the workbench view.
bullet 
Pressing [F2] in the test-suite tree now moves focus directly to the details field that is most relevant for the display name of the node.
bullet 
The new 'Procedure' qfs.client.renameClient in the standard library qfs.qft can be used to rename an SUT client after it connects. This is especially useful for an SUT that launches multiple sub-processes that connect as client:2, client:3 etc.
bullet 
The new special variable $_{qftest:skipnode} can be used to skip execution of a node.
bullet 
Hyperlinks in the Eclipse FormText widget are now recognized as sub-items.
bullet 
Advanced image checks are now also available to scripts via the new run-context method rc.checkImageAdvanced.
bullet 
The various rc.check* methods in the run-context now return the result of the evaluated condition.
bullet 
The image of a 'Check image' node in the test-suite and the run-log as well as screenshot images can now be opened in a separate window by double-clicking the image (run-log only) or clicking the respective button above the image.
bullet 
There is a new utility module for scripting called qf. It contains variants of commonly useful methods like isInstance and the ability to add messages to the run-log even when no run-context is available, e.g. in TestRunListener, Checker or Resolver implementations.
bullet 
Templates for procedure recording have become more powerful. Procedures can now be created conditionally by placing a @CONDITION tag with an arbitrary Jython or Groovy script in the comment.
bullet 
The 'Procedure' qfs.web.browser.settings.setProxy in the standard library qfs.qft now also supports passing a URL for automatic proxy configuration.

Bugs fixed:

bullet 
Switching execution to a different node in the debugger could unbalance the parent/child relationships of the associated nodes in the run-log.
bullet 
Setting and unsetting options at script level could mess up default option values.
bullet 
Improved double click replay for SWT on Windows.
bullet 
Some selection events for SWT now receive special treatment for focus handling.
bullet 
Empty lines at beginning of an SWT StyledText widget are now handled correctly on Linux.
bullet 
Errors in nested test-cases are now listed correctly in the report.
bullet 
Proxy server settings for Internet Explorer 9 are now working correctly.
bullet 
Image checks are now working correctly with Firefox 4.
bullet 
Javascript and authentication dialogs are now working correctly in Firefox 4.
bullet 
QF-Test now issues a warning each time you first try to modify a write-protected test-suite.
bullet 
Doctags for 'Dependency' nodes are now listed correctly in pkgdoc documentation.

Version 3.4M1 - February 3, 2011

New features:

bullet 
Groovy was updated to version 1.7.6.
bullet 
QF-Test now actively monitors the memory available in the Java VM for running tests. When available memory runs low, the test is aborted cleanly and the run-log is saved. This also prevents extreme slow-down when memory gets tight.
bullet 
To prevent running out of memory in the first place, QF-Test now splits run-logs automatically by default, based on the option 'Minimum size for automatic splitting (kB)'.
bullet 
Managing test-suites in the workbench has been improved. The tab for the active suite is now shown with a bold font, you can drag tabs to re-order test-suites and double-clicking to the right of existing tabs creates a new suite.
bullet 
The search dialog now has additional options for limiting the search and it is also possible to search all loaded test-suites at once. To prevent visual overload for the common case, the search dialog can now be toggled between simple and advanced mode.
bullet 
The debugger has been mostly integrated into the workbench, except for the variables view which still requires the separate debugger window.
bullet 
There is a new recording mode for web applications that tells QF-Test to ignore individual events and record entire GET or POST requests instead, which are then represented by the new 'Server HTTP request' node. Upon replay QF-Test interacts directly with the HTTP/HTTPS server without requiring a browser. This can be useful for load testing or mass data entry.
bullet 
For Swing and SWT components with an icon QF-Test now records a hash value derived from the icon image as an 'Extra feature'. As long as the icon remains stable this should lead to improved recognition, especially for toolbar buttons without a label. The default state of the image hash extra feature is 'Should match'. You can change it to 'Ignore' for components where the icon is not reliable and to 'Must match' for components where the image is the best way to identify the component.
bullet 
There is a new special variable syntax that allows specifying a default value for a variable. This is extremely useful for things like generic components or really every place where a variable has a reasonable default, because that default value is then tightly coupled with the variable lookup itself and doesn't have to be specified at 'Sequence' or test-suite level. The syntax is ${default:varname:defaultvalue}.
bullet 
Additional special variables are now available to retrieve the name of the currently executing 'Test-set' or 'Test-step' in addition to the already available 'Test-case' name. Also, counters were added for the number of test-cases executed so far, failures etc.
bullet 
Where available, the dialog showing the methods available for a component now also displays the results of calling those methods that represent Java Bean values.
bullet 
The option 'Log successful advanced image checks' can be activated in order to store the results of a successful advanced image check in the run-log. This can be useful while tuning the parameters for an advanced image check algorithm.
bullet 
The new command line option -verbose [<level>] for batch execution with or without accessing a daemon causes QF-Test to print progress information during a test-run.
bullet 
The new 'Procedure' qfs.utils.dumpHeap in the standard library qfs.qft can be used to trigger a heap dump for the Java VM of the SUT when it uses too much memory. This can be detected with the help of the 'Procedure' qfs.utils.logMemory which now returns the amount of memory used.

Bugs fixed:

bullet 
When replaying mouse events without coordinates on items, QF-Test no longer targets the center of the item, but the position 5 pixels from the left, vertically centered. Apparently some events are sensitive to whether the click hits the text of an item and not just its bounding box, so short items in a broad column could cause problems.
bullet 
Calling stored procedures in a database could fail using the default Jython bindings.
bullet 
If the debugger was turned off for normal use, debugger-stepping after hitting a breakpoint could occasionally fail so the test simply continued.
bullet 
A positive search result for the type of an extra feature could cause an exception.
bullet 
Blank characters in names for saving external run-logs are now turned into an underscore because Windows doesn't handle trailing blanks in directory names gracefully.
bullet 
The input file for a 'CSV data file' node is now closed immediately after reading the data.
bullet 
Recursive procedure calls could cause problems when importing procedures or analyzing references.

Version 3.3.0 - November 30, 2010

Incompatible changes:

bullet 
Support for Java 1.4.2 had to be dropped in order to update Jython and Groovy. QF-Test now requires at least Java version 1.5.
bullet 
Interaction between Jython and Java has changed slightly between Jython 2.1 and 2.5 so occasionally scripts that worked in QF-Test may now fail or behave differently. We try to maintain compatibility where possible and provide a list of things to look out for.

New features:

bullet 
Jython was updated to version 2.5.1. Most scripts should continue to run without problems. Incompatibilities may arise due to the changes in character encoding and because Java strings are now uniformly treated as unicode strings in Jython.
bullet 
Groovy was updated to version 1.7.2.
bullet 
Support was added for Eclipse / SWT version 3.6.1.
bullet 
Experimental support was added for Firefox 4 and Internet Explorer 9.
bullet 
QF-Test now integrates well with the increasingly popular Continuous Integration system Hudson CI. This includes JUnit as an additional target format for QF-Test reports.
bullet 
Image checks are no longer restricted to testing for exact pixel-by-pixel equality. Several flexible algorithms now allow image checks with a configurable degree of deviation from the expected image.
bullet 
Besides components you can now also import test-cases and procedures from one test-suite into another.
bullet 
When coordinates for mouse events are irrelevant, QF-Test now removes them altogether instead of setting them to (1,1). Upon replay the event is then aimed at the center of the target component or item.
bullet 
By combining search and replace operations with marks it is now possible to narrow searches in several steps, giving very fine-grained control over where to perform replacements.
bullet 
Moving backwards or forwards between selected nodes now works across test-suites and even run-logs. Thus a single mouse click or keystroke is now sufficient to return when following a procedure call to its target in a different test-suite or when jumping from a run-log to the respective node in the suite.
bullet 
Several new toolbar buttons were added and all the buttons now look much better. The menu structure also was cleaned up with operations on tree nodes now collected under the new »Operations« menu, among them many new node transformations. Also, several new keyboard shortcuts were introduced.
bullet 
The layout of pkgdoc and testdoc documentation now equals that of reports, including node icons and support for test-steps. These can be configured via the command line arguments -testdoc.teststeps, -testdoc.nodeicons and -pkgdoc.nodeicons or the respective options in the dialog for interactive creation of those documents.
bullet 
'Skipped' and 'Not implemented' tests can now be ignored in the report via the command line argument -report.ignoreskipped or the respective option in the interactive dialog.
bullet 
Daemon tests can now be stopped at the command line via the new argument -stoprun.
bullet 
The comment of a 'Procedure', 'Test-case' or 'Dependency' node can now be filled automatically with doctags for parameters, characteristic variables and author by right-clicking the node and selecting »Additional node transactions«-»Fill comment« from the context menu.
bullet 
The TestRunListener API now also provides information about whether a test-run was terminated normally (with or without exceptions) or aborted.
bullet 
The new method rc.callTest in the run context can be used to call a 'Test-case' or 'Test-set'. In contrast to callProcedure, callTest can only be called from 'Server script' nodes. It returns the exit status of the called test.
bullet 
The content of QF-Test configuration files is now sorted which significantly improves handling of those files in a version control system.
bullet 
Several procedures were added to or refined in the standard library qfs.qft. Its documentation is now also available online and indexed by the full text search engine on the QFS website. A link to the online text search covering all technical material is provided via the menu »Help«-»Online search...«.
bullet 
It is now possible to create a test-suite from a run-log.
bullet 
It is now possible to pass GUI elements from an SUT script as individual targets to QF-Test's component recognition mechanism via the new run context method overrideElement.

Bugs fixed:

bullet 
When started from QF-Test, Internet Explorer 8 always ran in IE7 compatibility mode. This is no longer the case. Compatibility mode can now be actively selected in the quickstart wizard or via the procedure qfs.web.browser.settings.doStartupSettings in the standard library qfs.qft.
bullet 
On Linux QF-Test could sometimes crash SWT/Eclipse applications with disposed Combo popups.
bullet 
Test replay for Eclipse / SWT on Linux is now much more robust, especially when handling menus.
bullet 
Trailing empty newlines in StyledText widgets are now handled correctly on Linux.
bullet 
Creating reports with many screenshots now requires much less memory.
bullet 
Downloads in Internet Explorer should now work consistently.
bullet 
In case of overlapping nodes with transparent nodes on top QF-Test could pick the wrong node for check recording. It now lets the browser make the decision instead. Switching back to the old algorithm can be done via the option 'Let the browser determine the target element for check recording'.
bullet 
A memory leak in QF-Test resulting from SUT clients printing a lot of output to the shared terminal in workbench view was plugged.

Version 3.2.2 - July 15, 2010

New features:

bullet 
Support was added for testing Eclipse / SWT version 3.6 "Helios".
bullet 
Multiple file selection in an SWT FileDialog can now be recorded and replayed.

Bugs fixed:

bullet 
Replay performance could suffer severely if the user's home directory was located on a network drive.
bullet 
A workaround for an AWT weakness introduced in QF-Test 3.2.1 could impact replay performance for AWT/Swing.
bullet 
Yet another performance problem resulting from very large hierarchies of Swing menus has also been fixed.
bullet 
Several special cases for uploading files with Internet Explorer are now handled correctly.
bullet 
Downloading files with Internet Explorer now works correctly in case of HTTP redirection.

Version 3.2.1 - May 11, 2010

Bugs fixed:

bullet 
With a 1.4 JDK in interactive mode QF-Test would only start if given a file to open.
bullet 
Web-testing now works again on Windows 2000.
bullet 
The QF-Test debugger used to show duplicate entries on the variable stack for 'Procedure call' and 'Test call' nodes.
bullet 
There was a memory leak in connection with interactive editing of test-suites with 'Check image' nodes for large images.
bullet 
In very special cases an import of components into their own suite could result in incorrectly updated references.
bullet 
Saving entries for zipped run-logs could occasionally fail on Windows due to a problem in the underlying library. QF-Test now works around that.
bullet 
Two problems were fixed for SUTs with more than one GUI engine, e.g. a WebStart application or combined SWT/Swing. In such a case QF-Test used to log more than one screenshot of the main screen after an error and sometimes connections from the second engine could fail.
bullet 
The upload dialog for web pages was not handled correctly for all browser versions and the procedure qfs.web.input.fileUpload in the standard library qfs.qft did not handle all cases correctly.
bullet 
In recent QF-Test versions there was an inofficial global Jython run-context rc available in addition to the local one. In special cases this could cause subtle namespace problems, so the (still inofficial) global version was renamed to __rc.
bullet 
Several minor problems and occasional exceptions in connection with the result list dialogs were fixed.

New features in QF-Test version 3.2

Following is an overview over the main new features that have been implemented for QF-Test version 3.2. For detailed information about the differences between QF-Test 3.0 and 3.2, please see the release notes for versions 3.2.0 and 3.1.x.

bullet 
Support for Web testing in combination with Java applets
bullet 
JDK instrumentation is no longer required
bullet 
Workbench view for a modern user interface
bullet 
'Test-step' nodes for detailed reports
bullet 
Refactoring support with automatic update of references
bullet 
Integration with the open source test management tool TestLink
bullet 
New 'Best Practices' part in the manual
bullet 
Eclipse / SWT support updated for the latest versions including GEF
bullet 
Incremental search in all of QF-Test's text fields
bullet 
Result list dialogs for complex operations
bullet 
Component method spy
bullet 
Options can be set at script level
bullet 
Relative and test-suite-local procedures
bullet 
New-style 'Check' nodes and support for custom Checkers
bullet 
Static validation of references
bullet 
Automatic parameterization of procedures
bullet 
Persistent bookmarks and transient marks
bullet 
New APIs: ItemResolver, Checker, ClassNameResolver and TestRunListener

Version 3.2.0 - March 25, 2010

New features:

bullet 
Support for Eclipse / SWT has been brought up-to-date with the current versions 3.5.2 and 3.6M6.
bullet 
Swing components are no longer highlighted by exchanging their foreground and background color but by painting a rectangle, similar to SWT and Web. Target sub-items are now highlighted as well.
bullet 
The new 'Boolean check' node with 'Check type identifier' attribute 'visible' is similar to 'Wait for component to appear' node, but in contrast to the latter is is listed in the report as a check and it has different default settings for the result handling.
bullet 
The most recently accessed component and possibly item in the SUT can now be retrieved in Jython and Groovy 'SUT script' nodes via rc.getLastComponent() and rc.getLastItem().
bullet 
Selecting a file for upload in a web form can now be recorded and replayed directly on Windows. For a cross-platform implementation it is still necessary to call the procedure qfs.web.input.fileUpload from the standard library qfs.qft.
bullet 
Additional features were added to the result lists for complex operations. For example, you can now perform actual replacements in the result list for the replace dialog or you can update multiple failed checks at once from the error list in a run-log. Besides, the result list for an operation that takes time is now filled continuously and the operation can be aborted if necessary.
bullet 
Recent search expressions are now saved in the user configuration.
bullet 
'Dependency' nodes inside 'Packages' are now listed in the pkgdoc documentation unless disabled via the command line argument -pkgdoc.dependencies or the respective interactive option.

Bugs fixed:

bullet 
Right-clicks for Javascript-based popup menus no longer need to be replayed as hard events in order to trigger the popup reliably.
bullet 
When recording checks the z-order of DOM nodes is now properly taken into account so that QF-Test no longer records nodes that are actually in the background, covered by other nodes.

Version 3.1.4 - February 9, 2010

New features:

bullet 
It is no longer necessary to instrument standard JDKs or JREs, though it doesn't hurt to keep existing instrumentation.
bullet 
Support was added for the latest Eclipse / SWT version 3.6.
bullet 
QF-Test now supports Firefox 3.6.
bullet 
The new part II 'Best Practices' in the manual describes recommended procedures based on lessons learned from several customer projects and user feedback that will hopefully help you to find the best strategy for using QF-Test in your own projects.
bullet 
Reports have been restructured and further extended. 'Check' nodes now have an optional 'Name' attribute for their representation in the report. Besides, the performance of report creation has been drastically improved and its memory impact reduced.
bullet 
The tree display in run-logs now shows expanded values instead of variables. This can be toggled via the »View« menu.
bullet 
Compactification for run-logs is now more efficient and special placeholder log entries show where nodes were removed during compactification.
bullet 
Support for the Eclipse Graphical Editing Framework (GEF) is now included by default and works correctly with multiple concurrent GEF editors.
bullet 
The new procedure qfs.web.input.fileUpload in the standard library qfs.qft handles INPUT:FILE nodes for the various browser variants.
bullet 
TestLink integration has been simplified.
bullet 
For Swing and SWT tables and multi-column trees it is now possible to check a whole row at once.
bullet 
ExtraFeatureResolvers can now also be used for SWT and Swing.
bullet 
The standard library qfs.qft now includes wrapper procedures for the autowin module in the package qfs.autowin. These can be used to check for the existence of a window and to close it on Windows systems.
bullet 
The runid of the current test-run now is now available via ${qftest:runid}.
bullet 
Special variables or properties of type group:name can now be used for 'Characteristic variables'.
bullet 
For nodes like 'Test-step' or 'Test-set' with several tabs for variable bindings the number of bound variables is now displayed in the tab which makes it much easier to locate those bindings.

Bugs fixed:

bullet 
Several causes for IE crashes were fixed.
bullet 
Wait for absence now works correctly for invisible nodes.
bullet 
QF-Test doesn't get blocked as easily when the SUT generates a lot of output and the JTextArea for the shared terminal cannot keep up.
bullet 
The internal variable stack of QF-Test could get messed up in some special cases.
bullet 
The procedure builder now correctly handles '_' characters in package or class names.

Version 3.1.3 - December 1, 2009

New features:

bullet 
The new 'Test-step' node can be used to provide further structure and document tests below 'Test-cases'. 'Test-steps' are listed individually in the report unless deactivated with -report.teststeps. Similar effects can be achieved by marking arbitrary nodes with the doctag @teststep, optionally followed by a name for the step.
bullet 
The report now also can list checks (off by default) and warnings (excluding component recognition warnings, on by default) integrated into the test-step listing and also shows icons for nodes. The respective settings can be changed via -report.checks, -report.warnings and -report.nodeicons in batch mode or the respective options in the dialog for interactive report creation.
bullet 
In the workbench view there is now a context menu for the test-suite tabs.
bullet 
All 'Comment' attributes can now be edited in an external editor similar to scripts.
bullet 
There are new toolbar buttons in the run-log window for navigating to the next/previous error or warning.
bullet 
The incremental search feature now has more intelligent scrolling for hits and also allows scrolling the component being searched via the [Up], [Down], [Page up] and [Page down] keys.
bullet 
'Dependencies' can now optionally be resolved in a namespace which allows having different sets of dependencies for different parts of a test so that the dependencies don't interfere with each other. See the 'Dependency namespace' attribute for details.

Bugs fixed:

bullet 
Due to the JIDE libraries used, the new workbench view does not work with JDK 1.4. It now gets deactivated automatically when starting QF-Test with a 1.4 JDK.
bullet 
Several exceptions caused by the new workbench view and the multi result dialogs were fixed.
bullet 
Text checks for SWT Group widgets were missing.
bullet 
Fixed automatic scrolling of web pages for image checks and replay of hard events.
bullet 
The popup sub-menu for setting and removing marks was sometimes empty.

Patch 3.1.2-p1 - October 20, 2009

Bugs fixed:

bullet 
In the new workbench view QF-Test could lose track about which suites are currently loaded, causing a suite to get loaded more than once, leading to confusing behavior and sometimes an exception.
bullet 
The new mechanism for on-the-fly SWT instrumentation only handled one SWT plugin, so that in case of a multi-platform Eclipse based application with several SWT plugins the correct plugin for the current platform could remain uninstrumented.
bullet 
Calling stopRun could cause the shared run-context in the QF-Test daemon to become unusable.

Version 3.1.2 - October 15, 2009

New features:

bullet 
Support was added for the latest Eclipse / SWT version 3.5.1.
bullet 
We have started work on special support for several AJAX web toolkits, including Ext GWT, Ext JS, GWT, qooxdoo and RAP. Instead of deeply nested hierarchies of <DIV> nodes QF-Test now operates in terms of the actual rich interface of buttons, labels, trees etc. For information on how to activate this feature in its current state, please get in touch with QFS.
bullet 
QF-Test now comes with support for interacting with the open source test management tool TestLink.
bullet 
By default QF-Test now starts with a "Workbench View" where all open test-suites are arranged as tabs in a single window. This feature is work in progress. In case it causes problems or if you prefer the old style, you can switch back to multiple windows via the »View« menu.
bullet 
The new function »Analyze references« in the context menu of a node can be used to statically validate the correctness of a test-suite by verifying the existence of the target nodes of 'Procedure calls', 'Test calls', 'Dependency references' and references to 'Components'.
bullet 
Operations that search for or result in changes to multiple nodes now bring up a mass result dialog listing the affected nodes. You can either navigate to specific nodes directly from that dialog or use it to set marks on some or all of the resulting nodes.
bullet 
Nodes in a test-suite can now be marked with markers in four different colors for easier reference and quick navigation. Marks can be set either individually via the menu »Edit«-»Marks« or the context menu, or from a mass result dialog.
bullet 
All text fields, terminals etc. in QF-Test's user interface can now be searched locally by pressing [Ctrl-F] when the field owns the keyboard focus.
bullet 
The new Component Method Spy retrieves and displays fields and methods of Swing or SWT components as well as the Javascript properties of a DOM node in the web client.
bullet 
After recording a new sequence and transforming it into a 'Procedure' you can select »Parameterize node« from its context menu to tell QF-Test to automatically extract parameters for it from the contained nodes.
bullet 
The Eclipse / SWT instrumentation performed by the 'Procedure' qfs.qft#qfs.swt.instrument.setup now operates on-the-fly, building a new plugin from an existing plugin and the QF-Test specific add-ons. Thus it is now possible to instrument custom SWT plugins or plugins for unofficial Eclipse versions for which QF-Test doesn't provide an exactly matching instrumented plugin.
bullet 
Event nodes can now be transformed into a 'Wait for component to appear' node.
bullet 
The keyboard shortcut for the 'Redo' operation was changed from [Ctrl-R] to [Ctrl-Y]. Over the last years the latter has become a de facto standard.
bullet 
The warning about nested 'Test-case' execution can now be suppressed via the option "Log warning for nested test-cases".
bullet 
Where scrolling a web page is required to perform a hard event or an image check, QF-Test now tries to scroll a web page itself via Javascript calls instead of relying on the browser's internal mechanism which often completely messes up the display.
bullet 
Component recognition based on geometry can now be suppressed by setting the coordinate and size attributes of a 'Component' to '-'.
bullet 
It is now possible to specify just the 'Class count' or 'Class index' of a 'Component' node and ignore the other.

Bugs fixed:

bullet 
Using the replace dialog to replace a regular expression with an empty string caused an exception.
bullet 
The function to make 'Procedure calls' or 'Dependency references' relative did not work reliably.
bullet 
When moving several 'Procedures', the automatic correction of 'Procedure calls' could fail in some special cases.
bullet 
Procedure recording now works correctly for custom classes with a special ClassLoader.
bullet 
When creating reports, warnings can be suppressed entirely by specifying -report.warnings=false for batch mode or deactivating the respective option in the dialog for interactive report generation.
bullet 
Recording a click on an editable SWT table cell could cause the cell editor to get activated in the wrong table row.
bullet 
'Fetch index' nodes were not implemented for SWT.
bullet 
Removing or marking unused components, importing and other complex component operations could fail if the test-suite contained a 'Data table' node with no columns or empty table cells.

Add-on for Eclipse / SWT 3.5.1 - September 30, 2009

New features:

bullet 
This add-on adds support for Eclipse / SWT 3.5.1 "Galileo".

Version 3.1.1 - July 28, 2009

Incompatible changes:

bullet 
The changes to the check system described below are fully backwards compatible. However, once a test-suite has been saved with QF-Test version 3.1.1 it cannot be run correctly with an older QF-Test version except for QF-Test version 3.0.3 which has explicit bidirectional compatibility support for this feature. Once you introduce QF-Test version 3.1.1 you can safely continue to work with QF-Test 3.0.3, but you should not use older versions like 3.1.0 or 3.0.2.

New features:

bullet 
The transition to the new check mechanism is now complete. Custom Checkers are now fully documented and can be created for all check data types. All 'Check' nodes now have a 'Check type identifier' attribute and the old 'Check editable', 'Check enabled' and 'Check selected' nodes were replaced with 'Boolean check' nodes with a matching 'Check type identifier'.
bullet 
It is now possible to bookmark test-suites, run-logs and individual nodes in a test-suite so they are directly accessible via the new sub-menu »File«-»Bookmarks«.
bullet 
The new ClassNameResolver - though also useful for SWT and Swing applications - is an important milestone for AJAX web testing. With its help and the new pseudo class hierarchy for DOM nodes a deeply nested hierarchy of DIV nodes can be turned into a concise component hierarchy with expressive class names that vastly improve component recognition.
bullet 
'Procedures' can now automatically be parameterized via the sub-menu »Parameterize node« in the popup menu for the 'Procedure' node. This feature is work in progress and will need more fine-tuning so we hope for your feedback.
bullet 
When creating testdoc documentation it is now possible to follow 'Test call' nodes and include the target 'Test-case', 'Test-set' or test-suite into the generated documentation by activating the respective option in the dialog for interactive use or via the command line argument -testdoc.followcalls in batch mode.
bullet 
Several more variants for converting and (un)packing nodes were added.

Bugs fixed:

bullet 
Several problems with split run-logs were fixed. Log entries could get lost in compact logs, when the split run-log was not saved as a zip file or when split run-logs were disabled but the attribute 'Name for separate run-log' was defined.
bullet 
DaemonTestRunListeners did not work correctly in asynchronous mode.
bullet 
When creating a report, screenshots for failed 'Check image' nodes were always saved regardless of whether the failed check actually represented an error or was just a part of a conditional construct.
bullet 
Use of the new Java regular expressions in QF-Test's replace dialog was not correct so that some replacements based on regexps were not possible.
bullet 
When determining uniqueness of "id" attributes for use as names, QF-Test was too strict so that in some cases potential names were not assigned.
bullet 
Instrumenting an OpenJDK directory now works.
bullet 
Waiting for a new document did not handle the window name attribute correctly.
bullet 
Waiting for a download to finish always waited for the full timeout.
bullet 
In very rare cases replaying text input could crash an SWT application on Linux.
bullet 
Option settings from rc.setOption() in the SUT were reset whenever options were changed in the option dialog.
bullet 
Event replay for SWT MenuItems with Gtk 2.4 on RedHat Enterprise Linux 4 was not reliable.
bullet 
The ktable and gef Jython modules for the respective SWT components were not correctly updated for the new ItemResolver and Checker mechanisms.
bullet 
QF-Test now properly discerns the most modal SWT Shell in case multiple modal Shells are opened simultaneously.

Patch 3.1.0-p1 - June 25, 2009

New features:

bullet 
The primary cause for this patch release is its support for Eclipse 3.5 "Galileo".

Version 3.1.0 - May 19, 2009

Incompatible changes:

bullet 
QF-Test now uses standard Java regular expressions by default which are much more powerful than the old GNU regexp package. One major difference is that '{' and '}' are special characters for Java regexps and may need to be escaped with a '\'. If necessary, you can switch back to the old GNU regexps via the option "Use old-style GNU regexps (from before QF-Test version 3.1)".
bullet 
In contrast to Mozilla, Internet Explorer reports a local navigation to an anchor on the current page as a normal navigation event, so up to now a 'Wait for document to load' node was recorded which failed when replaying the same test on Mozilla. QF-Test now treats this situation uniformly by ignoring the extra navigation from IE so no 'Wait for document to load' node is recorded with either browser. Consequently, old 'Wait for document to load' nodes for local navigation will now fail and need to be removed from your tests.

New features:

bullet 
QF-Test's embedded browser for web testing now supports Java applets with JDK 1.6.0_10 and up, so QF-Test can now test the interaction of a web application with its embedded Java applet.
bullet 
Many of QF-Test's options, specifically those with an impact on test execution, can now be changed at run-time via the new run-context method rc.setOption.
bullet 
When moving 'Procedure', 'Dependency' or 'Test-case' nodes, all references to these nodes can now be updated automatically. Similar updates are now performed when changing the name of such nodes or 'Component' IDs via the replace dialog. As an additional feature the new special Variable group ${id:...} and the run-context method rc.id can be used to mark arbitrary text as the definition of a component id that will be updated whenever the referenced component changes.
bullet 
'Procedure calls' from one 'Procedure' to another 'Procedure' in the same 'Package' hierarchy can now use a relative procedure name. Also, 'Procedures' and 'Packages' can now be made local to their test-suite by prefixing the name with an '_'.
bullet 
The selection dialog for a 'Procedure', 'Dependency' or 'Test-case' node now also shows the comment of the selected node. Also, it is now possible to select multiple nodes in order to insert multiple calls at once.
bullet 
A 'Procedure call' to a specific 'Procedure' can now be created by copying the 'Procedure' node and pasting it to a place where insertion of the 'Procedure' is not allowed, which is basically everywhere a 'Procedure call' is allowed except for the 'Extras' node. Dragging and dropping a 'Procedure' with the same effect is also supported.
bullet 
It is now possible to interact directly with the Javascript engine of the browser and execute arbitrary scripts via the methods DomNode.toJs, DomNode.evalJs and DocumentNode.evalJs.
bullet 
When an error or exception occurs, the run-log now contains a stacktrace node, showing all nodes on the execution stack including their variable bindings, similar to the variables view in the debugger window.
bullet 
There is a new API for various kinds of resolvers and checkers, including an ItemResolver interface for implementing your own sub-items of custom components and a Checker interface for custom checks that can be captured and replayed just like QF-Test's standard checks.
bullet 
The new TestRunListener API can be used to monitor a test-run from a script. Its variant DaemonTestRunListener supports the same remotely via QF-Test's daemon API.
bullet 
Support for Eclipse / SWT now includes the latest Eclipse milestone 3.5M7.
bullet 
The run-context method rc.callProcedure now also works from an 'SUT script' in a web application.
bullet 
Execution of a 'Test-case' or 'Test-set' can now be aborted or skipped via the run-context methods rc.skipTestCase, rc.skipTestSet, rc.stopTestCase and rc.stopTestSet, e.g. to prevent wasted time and irrelevant error messages in case a dependency cannot be resolved.
bullet 
The name of the currently executing 'Test-case' is now available via the special variables ${qftest:testcase.name}, ${qftest:testcase.qname} and ${qftest:testcase.reportname}.
bullet 
Via the new methods setProperty and getProperty in the class Node from QF-Test's pseudo DOM API for web applications, arbitrary data can be associated with DOM nodes without affecting the web application.
bullet 
The new command line argument -ping for qftest -batch -calldaemon can be used to check whether a QF-Test daemon is up and running.

Bugs fixed:

bullet 
For SUTs running on Mac OS X QF-Test disables use of the screen menu bar to allow proper capture/replay of menu actions.
bullet 
Activating an engine license in the option dialog now works as expected.
bullet 
When recording procedures, a new root 'Package' is always created instead of merging the procedures into a possibly existing 'Package' named "procbuilder".

Version 3.0.3 - July 28, 2009

New features:

bullet 
Handling of 'Check' nodes is reverse-compatible with changes in QF-Test version 3.1.1 in which checks underwent a major overhaul. QF-Test version 3.0.3 can load, execute and save test-suites created with version 3.1.1 without losing information.

Bugs fixed:

bullet 
Several problems with split run-logs were fixed. Log entries could get lost in compact logs, when the split run-log was not saved as a zip file or when split run-logs were disabled but the attribute 'Name for separate run-log' was defined.
bullet 
When determining uniqueness of "id" attributes for use as names, QF-Test was too strict so that in some cases potential names were not assigned.
bullet 
JDK instrumentation now also works for an OpenJDK directory.
bullet 
Waiting for a new document did not handle the 'Name of the browser window' attribute correctly.
bullet 
Waiting for a download to finish always consumed the full timeout.
bullet 
Activating an engine license in the option dialog now works as expected.
bullet 
In very rare cases replaying text input could crash an SWT application on Linux.
bullet 
For SUTs running on Mac OS X QF-Test disables use of the screen menu bar to allow proper capture/replay of menu actions.

Patch 3.0.2-p2 - June 25, 2009

New features:

bullet 
The primary cause for this patch release is its support for Eclipse 3.5 "Galileo".

Bugs fixed:

bullet 
Event replay for SWT MenuItems with Gtk 2.4 on RedHat Enterprise Linux 4 was not reliable.
bullet 
QF-Test now properly discerns the most modal SWT Shell in case multiple modal Shells are opened simultaneously.

Patch 3.0.2-p1 - April 14, 2009

Bugs fixed:

bullet 
In QF-Test version 3.0.2 hard TAB characters in Jython or Groovy scripts were replaced with blanks when showing the script, immediately causing the respective node to become modified. This change has been taken back.
bullet 
With JDK 1.6 some of QF-Test's dialogs were not displayed with the correct size.

Version 3.0.2 - March 27, 2009

New features:

bullet 
Support was added for Eclipse / SWT versions 3.5M6 and 3.4.2.
bullet 
The method callProcedure was added to the class DaemonRunContext of QF-Test's daemon API. This method and the existing method runTest now also support direct passing of parameters to this call.

Bugs fixed:

bullet 
'Wait for document to load' nodes for web clients did not work reliably in case of multiple browser windows.
bullet 
Checking the enabled/disabled state of components is now also implemented for web clients.
bullet 
Capture and replay of MOVED and SIZED events is now also supported for browser windows of web clients.
bullet 
QF-Test now performs regular explicit garbage collections to prevent running out of memory in the PermGen Space, a special Java memory region that causes trouble for a lot of Java applications. For the SUT these extra garbage collections can be turned off via the option 'Automatically perform garbage collection in the SUT'.
bullet 
Disposal and recreation of an SWT Display is now handled correctly.
bullet 
Custom SWT Widgets implemented as an anonymous local class were not treated correctly, possibly leading to a ComponentNotFoundException.
bullet 
For checks with a very long timeout deadlock detection is now adjusted accordingly.
bullet 
The demonstration test-suite for integration with the Imbus TestBench was updated to the latest TestBench version and now handles split run-logs correctly.

Version 3.0.1 - January 23, 2009

New features:

bullet 
The Jython and Groovy run context rc now provides the convenience methods getBool, getInt, getNum and getString for simplifying lookup of typed variable values in scripts.
bullet 
It is now possible to specify proxy settings for a web SUT directly in the quickstart wizard or via the procedure qfs.web.browser.settings.setProxy in the standard library test-suite qfs.qft.
bullet 
An entry for Swing JInternalFrame components has been added to the template file for automatic procedure creation.

Bugs fixed:

bullet 
Web-testing with Mozilla on Linux no longer requires using a 1.4 JDK.
bullet 
Using the "Update component" feature for web pages with deeply nested tables could lead to duplicate component IDs.
bullet 
Left-to-right binding in 'Data table' and other data nodes has been fixed.
bullet 
SQL statements in 'Database' nodes did not work with Oracle databases, due to an automatically appended ';' character. This has been fixed. If your database engine requires that SQL statements are terminated with a ';' you have to specify it yourself.
bullet 
The procedure qfs.swt.instrument.setup now always picks the SWT plugin with an exact version match for instrumentation, if available. This is important for SWT 3.4, where versions 3.4.0 and 3.4.1 are mutually incompatible.
bullet 
When recording procedures, a '$' character displayed in one of the fields of the SUT could lead to an exception.
bullet 
Groovy class loading and script parsing in the SUT should now be faster, in some cases - specifically applets - drastically.
bullet 
A caught exception in the 'Finally' node of a 'Try' node could mess up the state of an exception caught earlier in a 'Catch' node.
bullet 
The demo test-suite swt_addressbook.qft was still based on SWT 3.1, support for which is no longer distributed with QF-Test. The suite is now based on SWT 3.4.

Version 3.0.0 - December 5, 2008

Major new features:

bullet 
Cross-platform and cross-browser web testing with web2.0/AJAX support.
bullet 
Integration with HP/Mercury Quality Center and Imbus TestBench.
bullet 
Groovy as a second scripting language.
bullet 
New Jython version 2.2.1.
bullet 
Improved Jython and Groovy script editor with syntax-highlighting.
bullet 
Automated creation of basic procedures.
bullet 
Extended and unified functionality for 'Check...' and 'Wait...' nodes.
bullet 
Direct support for negated checks.
bullet 
Split run-logs enable long-running tests without memory problems.
bullet 
64-bit support for SWT on Windows and Linux.
bullet 
Extensions and an external driver for the daemon API.
bullet 
New concept: "Expected failure" for 'Test-case' nodes.
bullet 
Directing and documenting manual tests.
bullet 
Extended undo support.
bullet 
Immediate vs. lazy variable bindings.
bullet 
Image API for creating and saving screenshots.
bullet 
Crypting of text input for password fields.
bullet 
Recursive sorting and transformation of nodes.
bullet 
Revised search with highlighting of results.
bullet 
Extensions to the standard library test-suite qfs.qft.
bullet 
New tutorial chapters for advanced features.

The life-cycle of a QF-Test version

There are different ways of handling the life-cycle of software that, like QF-Test, is widely used in production environments while continuously being maintained, improved and extended.

In the past we also worked with "Milestone" versions like 3.5M1 as steps towards a new version but for the current QF-Test version 4 decided to go back to the traditional "Beta" concept. Therefore the life-cycle for a QF-Test version is as follows:

Beta versions and release candidates

Development never stops. While the latest version is still being maintained, a new version evolves. When a number of new features has matured, typically a first Beta version is released, for example 4.0.0-beta1. More Beta releases like 4.0.0-beta2 with additional features may follow.

The version of QF-Test currently under development is the one that undergoes the most testing and generally can be considered as rather stable.

A helpful feature of Beta releases is that, during a limited time span, they can be used with a license valid only for the previous release, giving users without maintenance a chance to evaluate the new version without committing to anything.

Once the feature set of the new version is ready, one or more release candidates like 4.0.0-rc1 may follow where typically only minor details may differ from the final version.

"Dot-zero" and maintenance releases

When finally ready, a "dot-zero" version is released, 4.0.0 in this example. Having been available in the form of beta versions and release candidates for some time and not to forget our own "Quality First" test-automation efforts, QF-Test "dot-zero" releases are quite mature.

Maintenance releases like version 4.0.1 are released at irregular intervals, mostly to fix bugs but with extensions to the current feature-set. In case of a severe bug a maintenance version will be released as soon as the bug is fixed.

Patches

Sometimes small but annoying bugs are discovered soon after a release. They don't warrant a new release but are important enough to take care of. In such a case patch versions like 4.0.0-p1 are released to provide the latest changes to those who need them. Patches are announced on the QF-Test mailing list only (more about the QF-Test mailing list).

During development of new features or bug-fixes it is often necessary to solicit feedback from users. To that end, experimental patches are sometimes released to individual customers or, if of general interest, via the mailing list.

A patch is a very small set of changes relative to a given QF-Test version. It is provided in the form of a ZIP archive which is extracted over an existing QF-Test installation. There is only one ZIP file for all operating systems and installing a patch causes far less overhead than upgrading to a new QF-Test release.

A patch is always a temporary solution. The next full maintenance release will include all working fixes from patches since the last release and thus supersede previous patches.

We always run a full set of tests against official patches. However, due to the shorter release cycles patches cannot be quite as well tested as full releases. If you encounter problems after installing a patch, you can usually disable the patch by removing the file .../qftest/qftest-x.y.z/qflib/patch.jar. Please report all problems with patches to qftest-bug@qfs.de or to the mailing list.