Change: specify which user is making ruquests in yarns

1 files changed, 13 insertions, 13 deletions

diff --git a/yarns/100-happy.yarn b/yarns/100-happy.yarn
index 934f243..6e099ce 100644
--- a/yarns/100-happy.yarn
+++ b/yarns/100-happy.yarn
@@ -11,24 +11,24 @@ access token, which will be used for all requests.
 
 Check status.
 
-    WHEN user makes request GET /status
+    WHEN user tomjon makes request GET /status
     THEN status code is 200
     THEN response body is {"resources":0}
 
 Create a simple resource. Remember its id.
 
-    WHEN user makes request POST /res with body { "foo": "bar" }
+    WHEN user tomjon makes request POST /res with body { "foo": "bar" }
     THEN status code is 201
     THEN remember resource id as ID
     THEN remember resource revision as REV1
 
-    WHEN user makes request GET /status
+    WHEN user tomjon makes request GET /status
     THEN status code is 200
     THEN response body is {"resources":1}
 
 Retrieve the resource.
 
-    WHEN user makes request GET /res with header "Muck-Id: ${ID}"
+    WHEN user tomjon makes request GET /res with header "Muck-Id: ${ID}"
     THEN status code is 200
     THEN response body is { "foo": "bar" }
     THEN response has header "Muck-Id: ${ID}"
@@ -36,12 +36,12 @@ Retrieve the resource.
 
 Update the resource.
 
-    WHEN user makes request PUT /res with header "Muck-Id: ${ID}" and
+    WHEN user tomjon makes request PUT /res with header "Muck-Id: ${ID}" and
     ... header "Muck-Revision: wrong" and
     ... body { "foo": "foobar" }
     THEN status code is 400
 
-    WHEN user makes request PUT /res with header "Muck-Id: ${ID}" and
+    WHEN user tomjon makes request PUT /res with header "Muck-Id: ${ID}" and
     ... header "Muck-Revision: ${REV1}" and
     ... body { "foo": "foobar" }
     THEN status code is 200
@@ -49,7 +49,7 @@ Update the resource.
 
 Check the resource has been updated.
 
-    WHEN user makes request GET /res with header "Muck-Id: ${ID}"
+    WHEN user tomjon makes request GET /res with header "Muck-Id: ${ID}"
     THEN status code is 200
     THEN response body is { "foo": "foobar" }
     THEN response has header "Muck-Id: ${ID}"
@@ -58,7 +58,7 @@ Check the resource has been updated.
 Restart Muck. The resource should still exist.
 
     WHEN Muck is restarted
-    WHEN user makes request GET /res with header "Muck-Id: ${ID}"
+    WHEN user tomjon makes request GET /res with header "Muck-Id: ${ID}"
     THEN status code is 200
     THEN response body is { "foo": "foobar" }
     THEN response has header "Muck-Id: ${ID}"
@@ -67,7 +67,7 @@ Restart Muck. The resource should still exist.
 Search for the resource. First with a condition that is no longer
 true.
 
-    WHEN user makes request GET /search with body
+    WHEN user tomjon makes request GET /search with body
     ... {
     ...     "cond": [
     ...         {"where": "data", "field": "foo", "pattern": "bar", "op": "=="}
@@ -78,7 +78,7 @@ true.
 
 Now search for the correct value.
 
-    WHEN user makes request GET /search with body
+    WHEN user tomjon makes request GET /search with body
     ... {
     ...     "cond": [
     ...         {"where": "data", "field": "foo", "pattern": "foobar",
@@ -90,16 +90,16 @@ Now search for the correct value.
 
 Delete the resource.
 
-    WHEN user makes request DELETE /res with header "Muck-Id: ${ID}"
+    WHEN user tomjon makes request DELETE /res with header "Muck-Id: ${ID}"
     THEN status code is 200
 
-    WHEN user makes request GET /res with header "Muck-Id: ${ID}"
+    WHEN user tomjon makes request GET /res with header "Muck-Id: ${ID}"
     THEN status code is 404
 
 Restart Muck again. The resource should not exist.
 
     WHEN Muck is restarted
-    WHEN user makes request GET /res with header "Muck-Id: ${ID}"
+    WHEN user tomjon makes request GET /res with header "Muck-Id: ${ID}"
     THEN status code is 404
 
 All done.