0b10b7476c
The test function was temporarily blacklisted on Ubuntu, but also failing on other Linux platforms (e.g. openSuSE). It tested, whether closing all dock widgets and the main window, would close the application as well. It used one single shot timer, to close the windows and later one to check, whether the application was shut down. While that mechanism must work in an application environment, it is not guaranteed to work in testlib. More specifically, I could happen that the XCB / glib event loop continued to spin and wait for events. => Check the signal QGuiApplication::lastWindowClosed() instead. If the signal is fired, it is proven that all windows have been closed and the application would quit in a production environment. The underlying test case was: Application didn't quit with the last dock widget closed, because there was a dangling QDockWidgetGroupWindow. => finally: Clean up BLACKLIST Pick-to: 6.6 6.5 Change-Id: Ic5fde5967fc8dde70ab64dc30cc7367c908b5c51 Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io> |
||
|---|---|---|
| .. | ||
| auto | ||
| baseline | ||
| benchmarks | ||
| global | ||
| libfuzzer | ||
| manual | ||
| shared | ||
| testserver | ||
| CMakeLists.txt | ||
| README | ||
This directory contains autotests and benchmarks based on Qt Test. In order
to run the autotests reliably, you need to configure a desktop to match the
test environment that these tests are written for.
Linux X11:
* The user must be logged in to an active desktop; you can't run the
autotests without a valid DISPLAY that allows X11 connections.
* The tests are run against a KDE3 or KDE4 desktop.
* Window manager uses "click to focus", and not "focus follows mouse". Many
tests move the mouse cursor around and expect this to not affect focus
and activation.
* Disable "click to activate", i.e., when a window is opened, the window
manager should automatically activate it (give it input focus) and not
wait for the user to click the window.