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>

0 files changed, 0 insertions, 0 deletions