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 4.4.0 released
Dear QF-Test users, for the benefit of those that don't receive our newsletter the technical details of new medium or major QF-Test releases are also announced on this mailing list. My apologies if you receive this information twice. This medium upgrade adds procedures and a scripting module for controlling macOS applications. Eclipse/SWT support now includes version 2018-09, the 'Unit test' node handles JUnit 5 "Jupiter" tests and in PDF documents an entire text page can now be checked in a single step. Please see below for detailed release notes. Users with a valid Maintenance Agreement are entitled to this medium upgrade for free. If you already have a license for QF-Test version 4.3, you can directly install the new QF-Test version. Future QF-Test versions that are released within your maintenance period can then also be used permanently without upgrading your license. The full newsletter is also available online at https://www.qfs.de/en/about-qfs/news/newsletters/newsletter-2018-10-11-qf-test-44-released.html Should you be interested in subscribing to the full newsletter please send an informal email with subject "Subscribe Newsletter" to <newsletter@?.de>. Release Notes for QF-Test 4.4.0 =============================== New features: ------------- * The new automac module can be used to control native macOS applications at script level. It is accompanied by procedures in the package qfs.automac of the standard library qfs.qft. See manual chapter 28 for further information. * Support was added for Eclipse/SWT version 4.9 alias "2018-09". * The 'Unit test' node can now run unit tests using the JUnit 5 "Jupiter" engine. * New text checks for PDF documents add the ability to check the text of an entire page with a single 'Check text' or 'Check items' node. * GeckoDriver was updated to version 0.23.0 (for Firefox up to version 62) and ChromeDriver to version 2.42 (for Chrome up to version 69). * The arguments of TestRunListener methods can now easily be converted to Json objects and for a TestRunEvent a call to getNode().getComponentId() now returns the QF-Test component ID of the current step. See manual section 46.7 for details. Bugs fixed: ----------- * Auto-filling the comment of a procedure could accidentally drop @author information and other doctags. * In special cases the call to rc.toServer in a Jython 'SUT script' node could cause a NullPointerException. * The result of a 'Fetch index' step for first-level child nodes of a Tree or TreeTable component in a web application wasn't always correct. * With Internet Explorer a download triggered in a popup window could remain incomplete. * Computing the name of an embedded Swing Frame based on the containing JavaFX SwingNode now also works with JavaFX 11. -- Gregor Schmid E: gregor.schmid@?.de T: +49 8171 38648-11 F: +49 8171 38648-16 Quality First Software GmbH | www.qfs.de Tulpenstr. 41 | 82538 Geretsried | Germany GF Gregor Schmid, Dr. Martina 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.