From 33407ae00d7500255cd38b3c02a33a3f7359e9e2 Mon Sep 17 00:00:00 2001 From: Frederik Gladhorn Date: Tue, 4 Oct 2016 10:17:49 +0200 Subject: Run tst_TouchMouse::buttonOnDelayedPressFlickable with both scenarios I commented the first data row out when debugging, it should have been active in the commit. Change-Id: I18ffc1ef4f67cd48a4bfbd9ec23362e07df32c7f Reviewed-by: Shawn Rutledge --- tests/auto/quick/touchmouse/tst_touchmouse.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'tests/auto/quick/touchmouse') diff --git a/tests/auto/quick/touchmouse/tst_touchmouse.cpp b/tests/auto/quick/touchmouse/tst_touchmouse.cpp index 5cd2187db5..309c01dcdc 100644 --- a/tests/auto/quick/touchmouse/tst_touchmouse.cpp +++ b/tests/auto/quick/touchmouse/tst_touchmouse.cpp @@ -618,7 +618,7 @@ void tst_TouchMouse::buttonOnDelayedPressFlickable_data() // the item should never see the event, // due to the pressDelay which never delivers if we start moving -// QTest::newRow("scroll before press delay is over") << true; + QTest::newRow("scroll before press delay is over") << true; // wait until the "button" sees the press but then // start moving: the button gets a press and cancel event -- cgit v1.2.3