d203f82916
Some of the mockplugin tests needed to be excluded from the unity build manually. In addition, MSVC's complain about include <QtCore/QString> instead of <QString> was addressed here since it was breaking the unity build as well. Some other independent executable and libraries have to be excluded manually as well. Pick-to: 6.5 Task-number: QTBUG-109394 Change-Id: I1f21f8484b4d3b1c399e2118ab3a71e682a3006a Reviewed-by: Joerg Bornemann <joerg.bornemann@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.