summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2019-05-10 11:42:09 +0300
committerLars Wirzenius <liw@liw.fi>2019-05-10 11:42:09 +0300
commitffe95f81b462c3ff0d08de37b3b9e4ce4ccfa93a (patch)
treec6d19603a4ddc18bd233238e32fbbca9404809d7
parent826b8879beda910235d0594139c423c30f77ada1 (diff)
downloadsaga-poc-ffe95f81b462c3ff0d08de37b3b9e4ce4ccfa93a.tar.gz
Change: first all ASSUMINGs, then all USINGs, then the rest
-rw-r--r--saga.pdfbin145520 -> 145672 bytes
-rw-r--r--saga.yarn5
2 files changed, 5 insertions, 0 deletions
diff --git a/saga.pdf b/saga.pdf
index b6ac54a..57a7e23 100644
--- a/saga.pdf
+++ b/saga.pdf
Binary files differ
diff --git a/saga.yarn b/saga.yarn
index f3adb36..6bb7aa9 100644
--- a/saga.yarn
+++ b/saga.yarn
@@ -161,6 +161,8 @@ The keywords have the following meanings:
environment, or access to external services, but which can't be
required for all runs of the acceptance tests.
+ All ASSUMING steps MUST come first in the scenario.
+
* USING&mdash;indicate that the scenario uses a resource such as a
database, that's constrained and can't be used by all scenarios if
they run concurrently. When scenarios declare the resource, Saga can
@@ -175,6 +177,9 @@ The keywords have the following meanings:
The goal is to be simple and correct rather then get maximal
concurrency.)
+ All USING steps MUST come at the beginning of the scenario, except
+ the ASSUMING steps may precede them.
+
* GIVEN&mdash;set up the test environment for the action (WHEN). This
might create files, start a background process, or something like
that. This also sets up the reversal of the setup, so that any