0e5de43e10
This one isn't trivial, but straight-forward: the only place the container is modified is in fill(). Like the setOpaqueChildren() function, this is only called from top-level test functions, and, in particular, not from event handlers (setAttribute() sends events). That fill() doesn't clear() the container, even though the single UpdateWidget instance is being reused across test functions, looks wrong, but doesn't invalidate this analysis. Task-number: QTBUG-115803 Change-Id: I284a19da2fe476278986c61810dd334fc73034b0 Reviewed-by: Ahmad Samir <a.samirh78@gmail.com> Reviewed-by: Ivan Solovev <ivan.solovev@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.