1 files changed, 4 insertions, 4 deletions
diff --git a/yarns.webapp/050-troves.yarn b/yarns.webapp/050-troves.yarn
index 8737306..e2f89e8 100644
--- a/yarns.webapp/050-troves.yarn
+++ b/yarns.webapp/050-troves.yarn
@@ -36,7 +36,7 @@ reads that, it should list the added Trove in status.
 
     GIVEN lorry-controller.conf in CONFGIT adds trove example-trove
     AND lorry-controller.conf in CONFGIT has prefixmap example:example for example-trove
-    WHEN admin makes request POST /1.0/read-configuration with dummy=value
+    WHEN admin makes request POST /1.0/read-configuration
     AND admin makes request GET /1.0/status
     THEN response has troves item 0 field trovehost set to "example-trove"
 
@@ -48,7 +48,7 @@ repositories from the remote Trove.
 If we tell WEBAPP to fetch the list, we should see repositories.
 
     GIVEN remote Trove example-trove has repository example/foo
-    WHEN admin makes request POST /1.0/ls-troves with dummy=value
+    WHEN admin makes request POST /1.0/ls-troves
     AND admin makes request GET /1.0/list-queue
     THEN response has queue set to ["example/foo"]
 
@@ -56,7 +56,7 @@ If we re-read the configuration again, without any changes to it or to
 the fake Trove's repository list, the same Troves and Lorry specs
 should remain in STATEDB. (It wasn't always thus, due to a bug.)
 
-    WHEN admin makes request POST /1.0/read-configuration with dummy=value
+    WHEN admin makes request POST /1.0/read-configuration
     AND admin makes request GET /1.0/status
     THEN response has troves item 0 field trovehost set to "example-trove"
     WHEN admin makes request GET /1.0/list-queue
@@ -67,7 +67,7 @@ avoid disasters. However, it will be removed from the Trove's STATEDB,
 and it won't be lorried anymore.
 
     GIVEN remote Trove example-trove doesn't have repository example/foo
-    WHEN admin makes request POST /1.0/ls-troves with dummy=value
+    WHEN admin makes request POST /1.0/ls-troves
     AND admin makes request GET /1.0/list-queue
     THEN response has queue set to []