fdfa3b1141
The test assumes that resizing a QWidget to 0x0 will result in the QWindow ending up with that size, and hence not being exposed, but this is not the case. On a QWindow level we treat 0x0 as a trigger for the platform layer to set the default size, and the window ends up exposed. Ideally QWindows should allow 0x0 sizes, but this is a bigger change. In the meantime, we skip the tests so that other changes can be integrated without the test failing. Task-number: QTBUG-61953 Change-Id: Ib17187b4afd1b06eaa76653be18e93abea555b59 Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io> Reviewed-by: Gabriel de Dietrich <gabriel.dedietrich@qt.io> |
||
|---|---|---|
| .. | ||
| auto | ||
| baselineserver | ||
| benchmarks | ||
| global | ||
| manual | ||
| shared | ||
| README | ||
| tests.pro | ||
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.