ca254a0937
qWaitForWindowActive was called in two test functions without activating the relevant widget. This patch adds widget activation before calling qWaitForWindowActive. Helper function verifyColor: A loop made six comparison attempts of widget size, pixel color and image with a 200ms waiting time after each unsuccessful attempt. The widget size was tested at the beginning of the loop. The test was failed on the first size mismatch, which occurred when verifyColor was called before the widget was rendered. That has lead to flakiness (e.g. on openSuSE). This patch encapsules each check in a lambda and calls qWaitFor to ensure event processing until each condition has become true. Change-Id: Ic98f93c8acf41459bc728f2969fe8b01768048dd Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@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.