| qftestJUI - 1.08.2 |
Release notes for qftestJUI version 1.08.2
June 8th, 2005
New features:
* The stability of test replay in conjunction with popup windows like menus or combo boxes has been drastically improved. These popups are somewhat unstable and can be popped down or interfered with by "hard" events coming directly from the system, for example focus changes when some other window is opened or closed or when opening a window or menu directly under the system mouse cursor. qftestJUI now filters or delays such system events during replay to prevent those effects. In case of unwanted side effects, this filtering can be turned off with the option "Filter or delay hard events during replay".
* In batch mode, multiple suites can now be run in one go. Separate run-logs and/or reports will be written for each executed suite, so the result is similar to running the suites separately. However, if the test-suites are implemented accordingly, repeated startup of the SUT can be avoided which - in case of large application - can lead to significant reduce of time spent and resources used.
* The option "Wait for 'busy' GlassPane" now affects checks and various other nodes in addition to mouse and key events. This includes the Wait for component to appear node which can now be used to handle a busy GlassPane on an individual basis by waiting for a component covered by the pane.
* If the option "Sub-item format" is set to "Intelligent", the row index of a table cell is now always recorded as a numeric index.
* The new connection mechanism now also supports the old WebStart version 1.0.1.
* The convenience method ResolverRegistry.isInstance, used to determine class/instance relationships without having to import the class first, now accepts all kinds of Java objects, not just Components.
Bugs fixed:
* The handling of layered components in qftestJUI could deviate from that in the AWT in the case where a component covering other components is not registered to receive mouse events. qftestJUI now uses the same mechanism as the AWT to determine the receiver of an event.
* The popup pseudo-menu that qftestJUI brings up for recording checks in the SUT is now constrained to the visible screen.
* Accessing HTML documentation directly from qftestJUI didn't work with Firefox on Windows.
* Suppressing a component name by returning the empty string from a NameResolvers getComponentName method didn't work.
* Diagnostic logging is now disabled by default.
* Item nodes with a numeric, hierarchical tree index caused problems during replay.
* Not all qftestJUI exceptions were imported by default for use in Jython scripts.
* Keyboard focus traversal in qftestJUI, which got slightly hampered in version 1.08.1, is back to normal.
* When merging components by importing a test-suite, a number suffix in the parent part of the ID of an imported component ID is now removed if possible.
* A textual index for addressing a column in a table-header (not the table itself) was resolved to the wrong column in case the column order was changed manually.

|