46925f589f
The runtime doesn't complain if a required property is satisfied via a ValueSource or an Interceptor, so qmllint shouldn't complain either. Whether this really should apply to interceptors is debatable, but for now let's aim for consistency. And that a ValueSource can satifsy the requirement is arguably to be expected. Pick-to: 6.10 6.8 Fixes: QTBUG-139632 Change-Id: I355b8a48e6b9bc2749839267c3b799e8eba5d72f Reviewed-by: Olivier De Cannière <olivier.decanniere@qt.io> |
||
|---|---|---|
| .. | ||
| auto | ||
| baseline | ||
| benchmarks | ||
| global | ||
| libfuzzer/qml | ||
| manual | ||
| system | ||
| testapplications | ||
| CMakeLists.txt | ||
| README | ||
README
This directory contains autotests and benchmarks based on QTestlib. 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.