11ae4b70a1
Previous setup of the test was failing in minimal static build if built using the unity build because of the explicit inclusion of the qtcore source files. By removing them, it surfaced that QFileSystemEntry doesn't export all its necessary symbols for testing. So this patch does that, as well as removing the qtcore sources from the test. It also makes sense to make the test private. Pick-to: 6.5 Task-number: QTBUG-109394 Change-Id: Icdabe32485b7ce4ed6049bcc24918f531406b4bd Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io> 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.