summaryrefslogtreecommitdiff
path: root/testing/02-commands-config.yarn
diff options
context:
space:
mode:
authorRichard Maw <richard.maw@gmail.com>2017-01-02 12:11:56 +0000
committerRichard Maw <richard.maw@gmail.com>2017-01-02 12:34:26 +0000
commit40b9f6e0280053f1dbefddb3edc5000530b6269e (patch)
tree7f1585141e5df2bf47efe0a824815e0dc3d54059 /testing/02-commands-config.yarn
parente4e4a4fc0dfcce2d2aea47a7f862e1b375e7e098 (diff)
downloadgitano-40b9f6e0280053f1dbefddb3edc5000530b6269e.tar.gz
testing: Reformat yarns
We got some weird indentations because some code editors normalise whitespace and do so to different levels. This also took the opportunity to re-justify the text too.
Diffstat (limited to 'testing/02-commands-config.yarn')
-rw-r--r--testing/02-commands-config.yarn10
1 files changed, 5 insertions, 5 deletions
diff --git a/testing/02-commands-config.yarn b/testing/02-commands-config.yarn
index 1ffca23..2dbdf21 100644
--- a/testing/02-commands-config.yarn
+++ b/testing/02-commands-config.yarn
@@ -20,7 +20,7 @@ repository when created. `HEAD` is defaulted to `refs/heads/master` but the
owner can be set via the person running the create.
SCENARIO Viewing initial `config` for a repo
-
+
GIVEN a standard instance
WHEN testinstance adminkey runs create testrepo
AND testinstance adminkey runs config testrepo show
@@ -38,7 +38,7 @@ we configure a test repository with a value which is not default and then check
for it.
SCENARIO Configuration changes stick
-
+
GIVEN a standard instance
WHEN testinstance adminkey runs create testrepo
AND testinstance adminkey runs config testrepo set project.head refs/heads/trunk
@@ -69,7 +69,7 @@ when changing configuration, all relevant hook sections are run to update the
outside world.
SCENARIO Changes to `HEAD` and description hit the filesystem
-
+
GIVEN a standard instance
WHEN testinstance adminkey runs create testrepo
AND testinstance adminkey runs config testrepo set project.head refs/heads/trunk
@@ -86,7 +86,7 @@ Clod can contain lists in values. Lists are always one-level and can have
new items appended...
SCENARIO Manipulating list values is possible
-
+
GIVEN a standard instance
WHEN testinstance adminkey runs create testrepo
AND testinstance adminkey runs config testrepo set foo.* hello
@@ -102,7 +102,7 @@ new items appended...
AND testinstance adminkey runs config testrepo show
THEN stderr is empty
AND stdout contains foo.i_1: world
-
+
WHEN testinstance adminkey runs config testrepo rm foo.i_1
AND testinstance adminkey runs config testrepo show
THEN stderr is empty