Add yarn test for pretend backups

Remove cmdtest test for this.

To make things clearer in the new test, also change all the steps that
use a backup repository to have the user specify it explicitly.

1 files changed, 6 insertions, 5 deletions

diff --git a/yarns/0100-fuse.yarn b/yarns/0100-fuse.yarn
index 53ddd21c..1a4f6d88 100644
--- a/yarns/0100-fuse.yarn
+++ b/yarns/0100-fuse.yarn
@@ -9,8 +9,8 @@ test suite concentrates on verifying that at least the basics work.
     ASSUMING user is in group fuse
     GIVEN directory L with interesting filesystem objects
     AND a manifest of directory L in M
-    WHEN user backs up directory L
-    AND user FUSE mounts their repository at F
+    WHEN user backs up directory L to repository R
+    AND user FUSE mounts the repository R at F
     THEN L, restored to F/latest, matches manifest M
     FINALLY unmount repository F
 
@@ -23,9 +23,10 @@ We do the backup, and verify that it can be accessed correctly, by
 doing a manifest of the live data before the backup, and then
 against the FUSE mount, and comparing the two manifests.
 
-    IMPLEMENTS WHEN user FUSE mounts their repository at (\S+)
-    mkdir "$DATADIR/$MATCH_1"
-    run_obnam mount -r "$REPO" --to "$DATADIR/$MATCH_1" --viewmode multiple
+    IMPLEMENTS WHEN user FUSE mounts the repository (\S+) at (\S+)
+    mkdir "$DATADIR/$MATCH_2"
+    run_obnam mount -r "$DATADIR/$MATCH_1" \
+        --to "$DATADIR/$MATCH_2" --viewmode multiple
 
 If we did do the fuse mount, **always** unmount it, even when a step
 failed. We do not want failed test runs to leavo mounts lying around.