diff options
author | Shawn Rutledge <shawn.rutledge@qt.io> | 2017-11-08 11:51:02 +0100 |
---|---|---|
committer | Shawn Rutledge <shawn.rutledge@qt.io> | 2017-11-08 18:07:49 +0000 |
commit | 87253cb04612a3f97c779c0111c0e635e6c910ab (patch) | |
tree | d4bba512666d51a6567946fe2073c0111ae7f85b /examples/quick/textureprovider | |
parent | 54f15f5df5cf545bf4d675ccbafecd482b4a2b0b (diff) |
stabilize and optimize tst_QQuickListView::QTBUG_34576_velocityZero
- don't use QTRY_VERIFY or QTRY_COMPARE if there's nothing to wait for,
because it will always wait a short time and add needless delay to the test
- QVERIFY(QSignalSpy::wait())'s should perhaps not be done in sequence,
in case the second signal already happened while we were waiting for the first.
QTRY_VERIFY(QSignalSpy::count() > 0) should be more reliable in such a case,
as long as we are sure the count started at zero before the behavior
which was supposed to make the signal be emitted.
- 1000ms is probably not long enough to wait for ListView velocity change
on a slow CI system.
- according to the comment "verify that currentIndexChanged is triggered"
we need another spy for that signal.
Change-Id: I99d93a849b674ce6c81acbe91639f03933025117
Reviewed-by: Jan Arve Sæther <jan-arve.saether@qt.io>
Diffstat (limited to 'examples/quick/textureprovider')
0 files changed, 0 insertions, 0 deletions