Kari Oikarinen ae8743bf86 tst_QCommandLinkButton: Add back wait to the beginning of setAutoRepeat() ... setAutoRepeat() is failing on macOS and Windows when run together with defaultAndAutoDefault(). It succeeds when run on its own. Adding the wait allows it to succeed when run with the other tests as well. Amends 0cb940b1d3, which removed the wait. The comment is the same as before. I couldn't see a better way to replace the wait (QApplication::topLevelWidgets() already returns only the testWidget and testWidget->isActiveWindow() returns true). Another theory I had was something waiting for the KeyRelease so I changed QApplication::sendEvent() uses to QTest::keyClick(). It did not help but that still seems preferable. Change-Id: If87d1e6e018751f3068ea4c913ae6731aba41ff0 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>		2018-05-16 06:10:08 +00:00
..
dialogs	tests/auto/widgets/dialogs: Avoid unconditional qWait()s	2018-05-14 10:39:00 +00:00
effects	tests/auto/widgets/{effects,styles}: Avoid unconditional qWait()s	2018-04-25 05:47:01 +00:00
graphicsview	tests/auto/widgets/graphicsview: Avoid unconditional qWait()s	2018-05-14 06:05:19 +00:00
itemviews	tests/auto/widgets/itemviews: Avoid unconditional qWait()s	2018-05-09 05:52:22 +00:00
kernel	Blacklist tst_QWidget::raise on openSUSE	2018-05-09 13:05:54 +00:00
styles	tests/auto/widgets/{effects,styles}: Avoid unconditional qWait()s	2018-04-25 05:47:01 +00:00
util	tests/auto/widgets/util: Avoid unconditional qWait()s	2018-04-13 12:32:52 +00:00
widgets	tst_QCommandLinkButton: Add back wait to the beginning of setAutoRepeat()	2018-05-16 06:10:08 +00:00
widgets.pro	Move QGestureRecognizer test to widgets/kernel	2017-06-02 18:36:11 +00:00