081670b840
The single use of Q_FOREACH in this test is safe to port 1:1 to a ranged for-loop, since we're in a constructor, and the loop body only calls member functions of data members (incl. the base class), so we cannot possibly modify the container passed in as a constructor argument: any connections or event processing that could re-enter our caller hasn't been set up, yet. Task-number: QTBUG-115803 Change-Id: I7095aef1edddbda0d1b0c471192b18acd6fd1793 Reviewed-by: Fabian Kosmale <fabian.kosmale@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.