La liste de diffusion est fermée depuis juillet 2022, mais sert toujours d'archive d'informations sur QF-Test.
Cependant, si vous souhaitez rester informé des nouveautés concernant QF-Test, vous pouvez simplement vous abonner à la newsletter :
abonner à la newsletter
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [QF-Test] QF-Test version 3.5.7 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 3.5.7 released ============================== QF-Test version 3.5.7 is now available for download from http://www.qfs.de/en/qftest/download.html#3.5.7 This update primarily adds support for Eclipse version 4.4 "Luna" as well as for Firefox versions 31 and 32. Conclusion of the QF-Test 3.5 branch ==================================== Presumably version 3.5.7 is the last version of the QF-Test 3.5 branch, which will be closed with the official release of QF-Test 4.0.0, probably next week or the week after. Firefox versions 31 and 32 as well as Eclipse/SWT version 4.4 are the last versions that QF-Test 3.5 will support. If you need support for newer Firefox or Eclipse versions you need to upgrade to QF-Test 4. Please note that QF-Test 3.5.7 also supports Firefox version 31ESR, which is going to receive updates from the Mozilla Foundation for the next 42 weeks: https://www.mozilla.org/en-US/firefox/organizations/ Release Notes for QF-Test version 3.5.7 ======================================= New features: _____________ * Support was added for Firefox versions 31 and 32. * Eclipse/SWT support was added for Eclipse version 4.4 "Luna". * 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: ----------- * 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. * 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. * The check for the editable state of INPUT:TEXT, INPUT:PASSWORD and TEXTAREA nodes was missing for web clients. * The "All lines" check for Swing JTextArea components was not recorded correctly when clicking below the first line of text. * 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. * When toggling the disabled state of the selected node, modifications made but not confirmed in the detail view were silently discarded. * 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. -- 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. Cookies fonctionnels
Nous utilisons des cookies fonctionnels pour garantir la fonctionnalité de base du site web.
2. Cookies de performance et de statistique
Nous utilisons Matomo pour analyser et améliorer notre site web. Des cookies permettent une collection anonyme des informations qui nous aident à vous offrir un visite clair et facile à utiliser de nos pages web.
This cookie contains a unique, pseudonymized visitor ID internal to Matomo for recognizing repeat visitors.
This cookie is used to track from which website the anonymized user proceeded to any page or sub-page.
The Matomo session cookie is used to track the visitor's page requests during the session. The cookie is automatically deleted at the end of each session (website visit), at the latest after one day.
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.