The mailing list has been closed since July 2022, but continues to serve as an archive of information about QF-Test.
But if you want to stay informed about news about QF-Test, you can simply
Subscribe to Newsletter
To get up-to-date information about each release - including minor releases - you can
subscribe to the RSS feed or follow us on social media.
Alternatively, QF-Test also provides release information itself.
Another source of information is our blog, where there are current articles on general topics, on the company QFS and also various "how-tos"
subscribe to blog
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[QF-Test] QF-Test version 4.1.1 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. The full newsletter is also available online at https://www.qfs.de/en/about-qfs/news/newsletters/newsletter-2016-11-23-qf-test-411-released.html 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.1.1 Released =============================== QF-Test version 4.1.1 is now available for download from https://www.qfs.de/en/qf-test/download.html Besides fixing several bugs, this release also includes a number of new features, among them a handy new filter for quickly locating test-suites in large projects and improved key bindings for macOS. Release Notes for QF-Test Version 4.1.1 ======================================= New Features: ------------- * The project view now comes with a filter at the top of the tree that matches on test-suite names and limits the hierarchy accordingly, which is very useful for quickly finding test-suites in large projects. * On macOS all keyboard shortcuts should now be conforming to Mac standards and use Mac-friendly modifier keys. * Selenium WebDriver was updated to version 3.0.1. * The documentation and samples for keyword driven testing have been extended with a new example for behavior driven testing (BDT). * The parameters for the @rerun doctag were extended to include a newerrorlevel=keep option and the new keepfirst parameter. * The 'Execution timeout' attribute is now also available for 'Test-step' nodes. Bugs Fixed: ----------- * QF-Test did not start if the Java version for QF-Test was still instrumented by an older QF-Test version (pre 4.1). Though JRE instrumentation has been deprecated for many years, such a case is still possible. QF-Test now detects that situation and helps with deinstrumentation of the JRE. * The test for busy panes was missing when performing a check using the generic retry mechanism introduced in QF-Test 4.1.0. * When interactively selecting a component for an event node the current target was not pre-selected in the chooser dialog. * Trying to update failed checks from the error list after closing the originating run-log caused an unexpected exception. * When using the databinder.bindList API for performing data-driven testing, QF-Test now ignores empty lists instead of running a single iteration without data. * When importing test results into TestLink, skipped test-cases are now correctly reported as skipped. * The former WebDriver API was renamed to WebDriverConnection to avoid confusion with Selenium's WebDriver object. * The error message for expiration of a -timeout <milliseconds> command line argument of a batch call now clearly refers to the -timeout <milliseconds> argument instead of the root node of the test-suite. * In large projects editing component IDs in parameter tables no longer causes delays while QF-Test is looking for the component to highlight. * When searching through a project with an invalid regular expression many errors messages were shown instead of just one. * Short timeouts for visible false checks on components were not honored. * If the option "Instrument AWT EventQueue" is active, QF-Test now establishes a connection with the awt:security engine in case Java WebStart shows an authentication dialog. Please note that in such a case the 'GUI engine' attribute of the 'Wait for client to connect' node must be set to awt:security. * Class resolution for AJAX toolkits was broken for some special cases. * The editable check didn't work for TextFields in the PrimeFaces toolkit. * When recording a click that triggers an alert dialog in WebDriver mode, the order of the recorded events was not always correct. * Auto-detection for AJAX toolkit resolvers has been improved. It now prints concise messages to the terminal and cleanly handles the case when no toolkit is detected. -- 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