It’s done: QF-Test 4.0.0 is now complete and ready for download.
Highlights include support for the new GUI technology JavaFX, Google Chrome as the third browser besides Internet Explorer and Firefox, improved handling for Java WebStart and applets, jQuery UI as additionally supported AJAX framework, generic classes for components of all GUI engines, a multi-level sub-item concept named QPath, similar to XPath, support for the embedded browsers Java FX WebView and JxBrowser 4, an improved user interface with colored syntax highlighting and a new qfs.qft package for client-side ssh connections.
Release Notes
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: – New GUI engine: JavaFX – Support for Chrome browser on Windows – Improved support for Java WebStart and applets – Support for the AJAX framework jQuery UI – Uniform generic classes for components of all GUI engines – Multi-level sub-item concept with QPath, similar to XPath – Support for embedded browsers – Improved user interface with colored syntax highlighting – New package for client-side ssh connections
Version 4.0.0 – July 31, 2014
New features: – Support was added for Firefox versions 31 and 32. – A more user-friendly way of updating a QF-Test license is now available via the menu »Help«-»Update license…«. – 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. – 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. – 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. – 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. – 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: – 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. – 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. – Column header cells in JavaFX tables are now addressed correctly. – CheckBox elements inside JavaFX table cells or tree nodes are now recorded with the new @:CheckBox item syntax. – The check for the editable state of TextField, PasswordField and TextAreas nodes was missing for web clients. – A selection in a ComboBox that initiated a navigation to another page could cause Internet Explorer to crash. – Check recording in the browser did not work in an area covered by an invisible IFRAME. – Event synchronization for the AJAX toolkit Ext JS now handles modal dialogs correctly. – Replay of text input for INPUT elements of type ‘number’ has been fixed. – When defining proxy settings for Internet Explorer via the qfs.web.browser.settings.doStartupSettings procedure, proxy.pac files were not handled correctly. – 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. – The ‘All lines’ check for Swing JTextArea components was not recorded correctly when clicking below the first line of text. – 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. – 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’. – When toggling the disabled state of the selected node, modifications made but not confirmed in the detail view were silently discarded.