3a9c8665e5
StablePosition was in some cases recording a wrong position, as it was taking the framePosition and considering it to be the widget's position. That erroneous position was then used to place the window, resulting in a correct position but a wrong framePosition. Wait and check for the window.geometry() and the window.frameGeometry() to be different. If not the frame has not been updated, or there is no frame when there should be one. The test will most likely fail because of this. Fix flakiness on Opensuse 15 Pick-to: 6.5 Change-Id: I8e05ee7769de4efc2ac55ec7afbe366f76e325db Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io> (cherry picked from commit 21ef8bed6d738551c1a322e78366d3c347a0e09e) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> (cherry picked from commit e20364d6c92dc5b46cea3639a9bd4b744c07bf0c) |
||
|---|---|---|
| .. | ||
| 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.