5d19dfb915
Testcase appearsAndSort failed when running the complete testcase but not as single test. More irritating was the fact that the error was in QAbstractItemModelTester::headerDataChanged() but the affected test did not change any header nor does it use the blamed model... The reason for this is, that QAbstractProxyModel emits a queued headerDataChanged signal when the header item count changes and therefore only evaluated when the event loop is run. Fix it by calling processEvents() after the rowCount change in filterColumns(). Amends 72e802f3b0cc7a0f36fe3c445d401d38af97ca99 Change-Id: I10cb5aa9c40a6925113cc9c23616774bf15784a4 Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io> (cherry picked from commit cdc608359a54a4b286494c1563f3cd94609030c0) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
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.