Add test for multiple clients sharing a repository

As part of this, make every repository operation step require an
explicit client name. The v6 reference formats have a client
name embedded that is the hostname of my laptop, so make those tests
use that name. This fixes what would not have run previously on any
system that isn't named havelock. Oops.

1 files changed, 6 insertions, 6 deletions

diff --git a/yarns/0100-fuse.yarn b/yarns/0100-fuse.yarn
index 1a4f6d88..8efe3e40 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 to repository R
-    AND user FUSE mounts the repository R at F
+    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
     FINALLY unmount repository F
 
@@ -23,10 +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 the repository (\S+) at (\S+)
-    mkdir "$DATADIR/$MATCH_2"
-    run_obnam mount -r "$DATADIR/$MATCH_1" \
-        --to "$DATADIR/$MATCH_2" --viewmode multiple
+    IMPLEMENTS WHEN user (\S+) FUSE mounts the repository (\S+) at (\S+)
+    mkdir "$DATADIR/$MATCH_3"
+    run_obnam "$MATCH_1" mount -r "$DATADIR/$MATCH_2" \
+        --to "$DATADIR/$MATCH_3" --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.