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 Major Upgrade 5.0 released
Dear QF-Test users, QF-Test version 5.0.0 is now available for download from https://www.qfs.de/en/qf-test/download.html The full newsletter is also available online at https://www.qfs.de/en/about-qfs/news/newsletters/newsletter-2020-02-06-qf-test-version-50-released.html Should you be interested in subscribing to the full newsletter please send an informal email with subject "Subscribe Newsletter" to <newsletter@?.de>. Highlights of QF-Test version 5.0 ================================= * New Engine for Windows applications * Modernized User Interface of QF-Test * Tests with Java 14 * Test-suites with comments Comment node For licenses with four UI technologies the fifth technology is free of charge. Detailed release notes ====================== New Features ------------ * With the new Windows engine QF-Test can now test native Windows applications. * Support was added for testing applications based on Java 14. * The new 'Comment' node can be used to improve the structure and readability of test-suites and run-logs. * It is now possible to download a file via the new 'Save response to file' attribute of the 'Server HTTP request' node. * A package for Windows applications has been added to the standard library qfs.qft. * On Windows 10 QF-Test is now correctly displayed at scaled high resolution displays. * In the manual the chapter Web testing has been revised and a section (subsection 45.1.3) describing the procedure qfs.web.ajax.installCustomWebResolver of the standard library has been added. * The option "Show message dialog after..." now has a setting to show a message dialog also when a test run finishes successfully. * If the result dialog gets shown after a search the search dialog is now closed automatically. * The new procedure qfs.util.click in the standard library qfs.qft can be used to click at an arbitrary position on the screen. * You can now create an electron start sequence in the quickstart wizard that automatically detects the required ChromeDriver. * When copying a 'Procedure call', 'Test call' or 'Dependency reference' node the name of the target node is now also copied as text to the clipboard. * The bundled GeckoDriver has been updated to version 0.26.0. * On Windows tests with the Microsoft Edge 78 and newer are also possible in headless mode. * QF-Test supports now Opera 66 with Operadriver 79.0.3945.79. * The new variable engine.$(componentId) in the qftest special group makes it possible to find out which GUI-engine a component belongs to. * The project tree view in QF-Test now uses a natural sort order, respecting indexes and cases. * Data for several new mobile devices was added to the Mobile Emulation setup in the quickstart wizard. Bugs Fixed ---------- * An image might have been removed from the run-log in low-memory situations. * Fixed a sporadic exception that could appear when creating a test-suite from a run-log. * 'Finally' nodes inside a 'Try' now get executed even when an instant rerun gets triggered from within the 'Try' node. * ImageWrapper methods now log warnings whenever the method fails. * In very rare cases the [Ctrl] key might accidentally have stayed in pressed state after finishing replay. -- 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. 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.