de0b702d31
Introduce a new module `TestInternalPrivate`. Kitware's RunCMake allows to create more granular unit tests using `cmake -P` scripts instead of configuring, generating and building full projects. [ChangeLog][Third-Party Code] Add upstream cmake's RunCMake test infrastructure module to src/testinternal/3rdparty/cmake to aid in creation of cmake auto-tests. Change-Id: I08cb7c6dc6f61bde29f176d58295f4f660b34ca8 Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io> (cherry picked from commit 39e7946cb6562c6f9b1baf5c44b1694922d0538e) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> (cherry picked from commit 926abdce783542638dcfa59fa1f4218b9cf3a151) |
||
|---|---|---|
| .. | ||
| 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.