Commit 715be958 authored by David Edmundson's avatar David Edmundson

[kioslave/desktop] Attempt at making test more robust

Summary:
We have an unstable test.
KCoreDirLister has a timer involved set to 200ms

QTRY_VERIFY will fire when we have one change from the spy, but maybe
not everything if we explicitly wait and process maybe it will improve
things?

It's a bit of a random shot-in the dark.

Test Plan: Passes locally..but it always passed locally before

Reviewers: #plasma, kmaterka

Reviewed By: kmaterka

Subscribers: kmaterka, plasma-devel

Tags: #plasma

Differential Revision: https://phabricator.kde.org/D28183
parent 17153c4a
......@@ -167,7 +167,8 @@ private Q_SLOTS:
QTRY_COMPARE(spyFileRenamed.count(), 1);
QTRY_COMPARE(spyFileRenamedWithLocalPath.count(), 1);
// and then desktopnotifier notices something changed and emits KDirNotify::FilesAdded
QTRY_VERIFY(spyFilesAdded.count() >= 1); // can be 3, depending on kdirwatch's behaviour in desktopnotifier
QTest::qWait(250); // larger than KCoreDirLister::pendingUpdateTimer
QVERIFY(spyFilesAdded.count() >= 1); // can be 3, depending on kdirwatch's behaviour in desktopnotifier
// check that KDirLister now has the correct item (#382341)
if (lister) {
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment