The mailing list has been closed since July 2022, but continues to serve as an archive of information about QF-Test.
If you want to stay informed about news about QF-Test, you can simply subscribe to our newsletter:
Subscribe to Newsletter
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [QF-Test] QF-Test version 4.0.4 released
Dear QF-Test users, for the benefit of those that don't receive our newsletter the technical details of new QF-Test releases are also announced on this mailing list. My apologies if you receive this information twice. Should you be interested in subscribing to the full newsletter please send an informal email with subject "Subscribe Newsletter" to <newsletter@?.de>. QF-Test version 4.0.4 released ============================== QF-Test version 4.0.4 is now available for download from http://www.qfs.de/en/qftest/download.html Highlight for Linux users is the support for 64bit Firefox on Linux - the search for suitable 32bit libraries is over. Also included are the newly supported AJAX framework jQuery EasyUI and updates for Firefox 36 and 37 as well as for Eclipse/SWT 4.4 SR2. Release Notes for QF-Test version 4.0.4 ======================================= New features: ------------- * QF-Test now supports testing 64bit versions of Firefox on Linux. * Dedicated support was added for the AJAX UI framework jQuery EasyUI. * Support for Firefox has been updated to match the public release of Firefox version 36 and support for Firefox version 37 has been added. * Support for Eclipse/SWT 4.4 "Luna" has been updated for the Eclipse 4.4 SR2 release. * The Java version for starting QF-Test's browser wrapper is no longer limited to the one QF-Test itself is using. It can now be set in the attribute 'Executable' of the 'Start browser' node. This makes it easier to mix 32bit and 64bit Java versions or to use the System JRE for the browser in order to support embedded Java applets. * The special variable syntax ${qftest:32} (or its alias ${qftest:32bit}) can be used to test whether QF-Test is running in a 32bit Java VM, with the obvious counterparts ${qftest:64} and ${qftest:64bit} to check for 64bit VM. * The new command line argument -daemonrmiport <port> can be used to run the QF-Test daemon behind a firewall by specifying a dedicated port for the daemon's RMI communication in addition to the daemon lookup port that is set with -daemonport <port>. * The default value of the option "Wait for non-existent component (ms)" is now temporarily set to at least 30000 ms during SUT startup. Adding a 'Wait for component to appear' node to the SUT startup sequence is still recommended though. Bugs fixed: ----------- * When automatically updating references after refactoring, multi-level sub-item syntax was cut off after the second item level. * The new command 'Find/Remove unused callables' treated procedures called only from dependencies as unused. * The workaround for the Java 8 focus issues on Windows now handles the root cause instead of trying to keep the side effects under control. * The standard library procedures in the package qfs.web.browser.settings now explicitly check the browser parameter for validity instead of failing silently with no effect. * Chrome is now able to record 'Server HTTP request' and 'Browser HTTP request' nodes. * Chrome could crash when navigating to a previously visited page anew. * In some cases auto-expansion of tree nodes in Chrome could cause a deadlock. * When creating a new startup sequence with the quickstart wizard for the AJAX toolkit GWT the version for the GWT resolver was incorrectly set to 1 instead of 2. The same problem affected auto-detection for GWT. * The AJAX toolkit jQuery UI was not handled by the auto-detection mechanism for AJAX resolvers. -- Gregor Schmid E: gregor.schmid@?.de T: +49 (0)8171 38648-11 F: +49 (0)8171 38648-16 Quality First Software GmbH | www.qfs.de Tulpenstr. 41 | 82538 Geretsried | Germany GF Gregor Schmid, Karlheinz Kellerer HRB München 140833
|
1. Functional cookies
We use functional cookies to ensure the basic functionality of the website.
2. Performance and statistic cookies
We use Matomo for analyzing and optimizing our website. Cookies permit an anonymous collection of information that help us offering you a clear and user-friendly visit of our web pages.
This cookie contains a unique, pseudonymized visitor ID internal to Matomo for recognizing returning visitors.
This cookie is used to track from which website the anonymized user proceeded to our website.
The Matomo session cookie is used to track the visitor's page requests during the session.
is created and should be then directly deleted (used to check whether the visitor’s browser supports cookies).
short lived cookies used to temporarily store data for the visit.
short lived cookies used to temporarily store data for the visit.