1c53afb774
Doesn't test anything, just that it doesn't crash. Turns out we have a race between thread cancellation and normal exit (filed as QTBUG-127008). Worked around by adding an infinite loop to run(), after terminate(). Android doesn't support cancellation at all, and our Windows implementation hits QTBUG-127050, so skip the test on those platforms. Pick-to: 6.7 6.5 6.2 5.15 Change-Id: I47a635a31caaf116d3688f31b9b5c5875e9765f5 Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> (cherry picked from commit a9f7e75a2647732ff998f1c0d112682dbd5c4e28) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> |
||
|---|---|---|
| .. | ||
| 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.