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 4.0.11 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.11 Released =============================== QF-Test version 4.0.11 is now available for download from https://www.qfs.de/en/qftest/download.html This release mainly adds support for Eclipse/SWT 4.6 "Neon" and reestablishes compatibility with Java 9. Release Notes for QF-Test Version 4.0.11 ======================================== New features: ------------- * Support for Eclipse/SWT 4.6 "Neon" has been added based on Eclipse version 4.6M6. Note: The new mechanism for auto-scaling SWT-based UIs on high-DPI monitors is not supported by QF-Test yet and is deactivated by default when the SWT plugin in instrumented by QF-Test. It can be forced active by setting the system property swt.enable.autoScale=true but in that case test execution will be limited. * In case of an error or exception on Windows, information about the current Windows session is now added to the diagnostic log entry in the run-log. This should help understanding failures caused by a locked session as described in the FAQ "Hard mouse events and drag'n'drop operations do not work flawlessly, components cannot be found, the run-log contains black or corrupt screenshots. What do I have to take care about for test execution?". Bugs fixed: ----------- * QF-Test now again starts correctly with early access versions of Java 9. This was broken after changing the Java 9 versioning scheme. The value "9-ea" for the system property java.version does not contain the '.' character that QF-Test expected to find after the main version. * In some cases the record button could remain active even after the last SUT client terminated. * A few keystrokes for certain characters - e.g. '.' - were not replayed correctly as single events in QF-Test's Chrome browser. * When trying to launch a WebStart application in QF-Test's Chrome browser, the download dialog for the JNLP file appeared instead. * Automatically restoring a minimized SWT or web browser window before replay on Linux could trigger a Gtk error that caused the SUT to crash. -- 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