summaryrefslogtreecommitdiff
path: root/yarns.webapp/030-queue-management.yarn
diff options
context:
space:
mode:
Diffstat (limited to 'yarns.webapp/030-queue-management.yarn')
-rw-r--r--yarns.webapp/030-queue-management.yarn6
1 files changed, 3 insertions, 3 deletions
diff --git a/yarns.webapp/030-queue-management.yarn b/yarns.webapp/030-queue-management.yarn
index 5ee45e1..0f67e1c 100644
--- a/yarns.webapp/030-queue-management.yarn
+++ b/yarns.webapp/030-queue-management.yarn
@@ -13,11 +13,11 @@ new jobs, and later to start it again.
SCENARIO admin can start and stop WEBAPP job scheduling
GIVEN a running WEBAPP
WHEN admin makes request GET /1.0/status
- THEN response has running-queue set to false
+ THEN response has running_queue set to false
WHEN admin makes request GET /1.0/start-queue
AND admin makes request GET /1.0/status
- THEN response has running-queue set to true
+ THEN response has running_queue set to true
Further, the state change needs to be persistent across WEBAPP
instances, so we kill the WEBAPP that's currently running, and start a
@@ -28,7 +28,7 @@ new one, and verify that the `running-queue` status is still `true`.
GIVEN a running WEBAPP
WHEN admin makes request GET /1.0/status
- THEN response has running-queue set to true
+ THEN response has running_queue set to true
Finally, clean up.