summaryrefslogtreecommitdiff
path: root/yarns/branches-workspaces.yarn
diff options
context:
space:
mode:
authorTiago Gomes <tiago.gomes@codethink.co.uk>2015-11-23 10:15:49 +0000
committerTiago Gomes <tiago.gomes@codethink.co.uk>2015-11-25 17:01:58 +0000
commit38f356088ff85a2ca186704173f8a9fb5cf9db66 (patch)
treec5165e3e36835e34b46ba891baa101e3d19b3a15 /yarns/branches-workspaces.yarn
parentd71d4824ef57a97266eebc11320cfb38295f484a (diff)
downloadmorph-38f356088ff85a2ca186704173f8a9fb5cf9db66.tar.gz
Tests: rename git repository
Rename the git repository where the morphologies used for testing are kept, from morphs to definitions. Change-Id: Icd5fa6609ddec3993dd4c772cd916359843ef500
Diffstat (limited to 'yarns/branches-workspaces.yarn')
-rw-r--r--yarns/branches-workspaces.yarn6
1 files changed, 3 insertions, 3 deletions
diff --git a/yarns/branches-workspaces.yarn b/yarns/branches-workspaces.yarn
index 42ff1226..c15f4147 100644
--- a/yarns/branches-workspaces.yarn
+++ b/yarns/branches-workspaces.yarn
@@ -159,7 +159,7 @@ A CSV manifest can also be generated.
SCENARIO morph generates a csv manifest
GIVEN a git server
- WHEN morph generates a manifest for system systems/test-system.morph at ref HEAD in repository test:morphs
+ WHEN morph generates a manifest for system systems/test-system.morph at ref HEAD in repository test:definitions
THEN morph succeeded
AND the csv manifest is generated
@@ -193,7 +193,7 @@ a system is likely to have a reproducible result.
SCENARIO using morph certify
GIVEN a git server
- WHEN the user certifies the system systems/test-system.morph at ref HEAD in repository test:morphs
+ WHEN the user certifies the system systems/test-system.morph at ref HEAD in repository test:definitions
THEN morph succeeded
AND morph output Reproducibility certification PASSED
@@ -206,5 +206,5 @@ artifact in a system. This name includes the cache key of the artifact.
SCENARIO using morph list-artifacts
GIVEN a git server
- WHEN the user lists the artifacts which make up the system systems/test-system.morph at ref HEAD in repository test:morphs
+ WHEN the user lists the artifacts which make up the system systems/test-system.morph at ref HEAD in repository test:definitions
THEN morph succeeded