ea25b3962b
It's very flakey in CI: http://testresults.qt.io/grafana/goto/XZQAAPRSg What we want to test is whether Qt issues paint events in response to enabling an already enabled effect. Doing so via qWait will process both window system events and posted Qt events, and the former might include spontaneous paint events from the system that we can't control. Task-number: QTBUG-115945 Pick-to: 6.5 6.6 Change-Id: I65e5c6a4458e77b3bd2ad700c5caf6d441f4ca53 Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io> |
||
|---|---|---|
| .. | ||
| auto | ||
| baseline | ||
| benchmarks | ||
| global | ||
| libfuzzer | ||
| manual | ||
| shared | ||
| testserver | ||
| CMakeLists.txt | ||
| README | ||
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.