20d23f7003
On Wayland there is a special case when decorations are enabled, where we post an initial update request to ensure widgets are redrawn after the buffer is recreated (see af7b60ade5c4be81cbc58eb18307c017d5594071 in qtwayland). To make sure the test behaves the same on Wayland as on other platforms, we disable client-side decorations when running these tests. The flag is primarily required for the requestUpdate() test at the moment, but it is only queried once per application run, so it has to be set before any tests are run. Pick-to: 6.4 Fixes: QTBUG-100889 Change-Id: Ica6d744083ecae4a3722b6d04b956e7615f0dfe5 Reviewed-by: Inho Lee <inho.lee@qt.io> Reviewed-by: Paul Olav Tvete <paul.tvete@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.