f7089e691e
The helper function TestWidget::waitForPainted returned after the test widget had consumed the first paint event. In case of multiple paint events, QRegion paintedRegions did not match the entire region that was supposed to be painted. The test function children() failed/flaked due to that. This patch extends the helper function. After consumption of the first paint event, it processes events until the painted regions no longer change. Pick-to: 6.4 Fixes: QTBUG-108764 Change-Id: I54e14bb07725dd1f602cc93085da13836e3b7494 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.