summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorXipmix <576337-xipmix@users.noreply.gitlab.com>2022-04-09 15:09:53 +1000
committerXipmix <576337-xipmix@users.noreply.gitlab.com>2022-04-09 15:23:24 +1000
commitd3bdc9640bcfbea7a66f605ebd6b34acac5f5632 (patch)
tree8a52d73700a828c6e9b9e77040210a4b75512a4b
parent2be516a2ba99074465e489ecd8af00697c9a27d0 (diff)
downloadsubplot-d3bdc9640bcfbea7a66f605ebd6b34acac5f5632.tar.gz
Comma to break sentence into contrasting options
-rw-r--r--subplot.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/subplot.md b/subplot.md
index 69e0db8..dc2499c 100644
--- a/subplot.md
+++ b/subplot.md
@@ -479,7 +479,7 @@ When you are formulating your scenarios, it is common to try and use phraseology
along the lines of _if this happens then that is the case_ but this is not
language which works well with subplot. Scenarios describe what will happen in
the success case. As such we don't construct scenarios which say _if foo happens
-then the case fails_ instead we say _when I do the thing then foo does not happen_.
+then the case fails_, instead we say _when I do the thing then foo does not happen_.
This is a subtle but critical shift in the construction of your test cases which
will mean that they map more effectively to scenarios.