qt5base-lts/tests
Leander Beernaert 69fb4ae343 Distinguish between qt_plugin and regular plugins
If we do not encounter the load(qt_plugin) statement in the .pro file
but we do see the entry CONFIG+=plugin, treat the target as a regular
CMake library instead of treating it as a qt_plugin by default.

Change-Id: I67ad5c865a1a5ab691a6b0d86c2db4b686aa04dd
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
2019-10-28 09:20:37 +00:00
..
auto Distinguish between qt_plugin and regular plugins 2019-10-28 09:20:37 +00:00
baselineserver Merge remote-tracking branch 'origin/5.13' into 5.14 2019-09-09 07:51:49 +00:00
benchmarks Merge remote-tracking branch 'origin/dev' into wip/cmake 2019-10-14 17:46:34 +02:00
global
libfuzzer Fuzzing: Don't copy input data to QByteArray 2019-10-09 17:16:09 +02:00
manual Merge remote-tracking branch 'origin/dev' into wip/cmake 2019-10-17 09:41:36 +02:00
shared Remove usages of Q_OS_WINCE 2019-05-23 13:51:05 +02:00
testserver Share the common configurations among different modules 2019-07-01 01:09:42 +02:00
CMakeLists.txt Convert corelib plugin tests 2019-10-21 11:17:20 +00:00
README
tests.pro

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.