diff options
| author | Gatis Paeglis <gatis.paeglis@qt.io> | 2018-02-26 16:54:51 +0100 |
|---|---|---|
| committer | Shawn Rutledge <shawn.rutledge@qt.io> | 2018-03-08 06:30:23 +0000 |
| commit | d6b7e7f8574ed2a74b3b636e8d0b928be978e2f5 (patch) | |
| tree | fbef2f94f584bc8c6be45161fbe64b926942a657 /tests/auto/quick/qquickpathview | |
| parent | 6b877ec53f3308e4a685c43142fde951f81de02b (diff) | |
tests: refactor and un-blacklist tst_QQuickMouseArea::pressedMultipleButtons
It seems that qtestlib has never really supported mouse state
handling for multiple buttons (see QTBUG-64030). And the current
implementation of this test relied on QGuiApplication to generate
mouse releases when necessary. Since a37785ec7638e7485112b87dd7e767881fecc114,
qtestlib does not rely on QGuiApplication to deduce mouse button
state, but requires explicit mouse press/release events via
QTest::mouse* APIs, thus causing this auto test to fail.
Refactor the auto test to use QTest::mouse* APIs. This change depends
on a fix for QTBUG-64030.
Task-number: QTBUG-63786
Change-Id: Id24526714ec9716a0126e8288e5e8974074ebc9e
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
Diffstat (limited to 'tests/auto/quick/qquickpathview')
0 files changed, 0 insertions, 0 deletions