summaryrefslogtreecommitdiff
path: root/yarns/0100-fuse.yarn
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2014-02-25 08:37:57 +0000
committerLars Wirzenius <liw@liw.fi>2014-02-25 08:37:57 +0000
commitd2489623d055746354ab3023aec7f43ccde3b84d (patch)
tree745700721e1e6ad1dd382a97b1ea11418b9855a4 /yarns/0100-fuse.yarn
parent5ee9b902cb65144ed7ddd2b6709d1b888b15f6ef (diff)
downloadobnam-d2489623d055746354ab3023aec7f43ccde3b84d.tar.gz
Test FUSE .pid reading in yarns
Diffstat (limited to 'yarns/0100-fuse.yarn')
-rw-r--r--yarns/0100-fuse.yarn17
1 files changed, 17 insertions, 0 deletions
diff --git a/yarns/0100-fuse.yarn b/yarns/0100-fuse.yarn
index 375202b2..0653d08e 100644
--- a/yarns/0100-fuse.yarn
+++ b/yarns/0100-fuse.yarn
@@ -12,6 +12,23 @@ test suite concentrates on verifying that at least the basics work.
WHEN user U backs up directory L to repository R
AND user U FUSE mounts the repository R at F
THEN L, restored to F/latest, matches manifest M
+
+The FUSE view of the repository won't change while we have it mounted,
+even if we make a new backup.
+
+ GIVEN 100k of new data in directory L
+ AND a manifest of L in M2
+ WHEN user U backs up directory L to repository R
+ THEN L, restored to F/latest, matches manifest M
+
+However, if we read the file `F/.pid`, the FUSE plugin refreshes the
+view and we can now see the new backup.
+
+ WHEN user U reads file F/.pid
+ THEN L, restored to F/latest, matches manifest M2
+
+Clean up.
+
FINALLY unmount repository F
We can only run this test if the user is in the `fuse` group. This may