summaryrefslogtreecommitdiff
path: root/yarns/900-implementations.yarn
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2014-11-22 17:54:49 +0200
committerLars Wirzenius <liw@liw.fi>2014-11-22 17:54:49 +0200
commit25dcc4b2234ddb768b76a5f4bd928a4817022bb4 (patch)
tree13c89e1ff9b33135658f619c29c129859580ba4e /yarns/900-implementations.yarn
parent85a797cc7339e9d49d0d6eb75018d42fb9897113 (diff)
downloadjt-25dcc4b2234ddb768b76a5f4bd928a4817022bb4.tar.gz
Add scenario for multiple drafts
Diffstat (limited to 'yarns/900-implementations.yarn')
-rw-r--r--yarns/900-implementations.yarn20
1 files changed, 20 insertions, 0 deletions
diff --git a/yarns/900-implementations.yarn b/yarns/900-implementations.yarn
index 35398a6..80798af 100644
--- a/yarns/900-implementations.yarn
+++ b/yarns/900-implementations.yarn
@@ -65,6 +65,26 @@ user, and with specific settings to make the test suite run smoother.
--layout=pkb \
--no-git \
$MATCH_1
+ echo 0 > "$DATADIR/jt.exit"
+
+Sometimes we expect `jt` to fail. In that case, the scenario step
+shouldn't fail.
+
+ IMPLEMENTS WHEN I try to run jt (.*)
+ set +e
+ EDITOR=true \
+ "$SRCDIR/jt" --no-default-config \
+ --config "$DATADIR/source.conf" \
+ --config "$DATADIR/time.conf" \
+ --layout=pkb \
+ --no-git \
+ $MATCH_1
+ echo "$?" > "$DATADIR/jt.exit"
+
+Check that the latest invocation of `jt` didn't fail.
+
+ IMPLEMENTS THEN it fails
+ ! grep -Fx 0 "$DATADIR/jt.exit"
Checking file existence