diff options
Diffstat (limited to 'yarns/splitting.yarn')
| -rw-r--r-- | yarns/splitting.yarn | 17 |
1 files changed, 7 insertions, 10 deletions
diff --git a/yarns/splitting.yarn b/yarns/splitting.yarn index 75831e53..4342260b 100644 --- a/yarns/splitting.yarn +++ b/yarns/splitting.yarn @@ -8,8 +8,7 @@ To verify that the products fields are parsed correctly, we have a scenario that uses all of them, not relying on the default rules. SCENARIO building a system with morphologies that have splitting rules - GIVEN a workspace - AND a git server + GIVEN a git server To test that all the fields are recognised, we set the new fields to their default values. @@ -22,7 +21,7 @@ The default rules produce a system that is identical to not providing them, and since this test is about validation, we don't care about the result, so much as it succeeding to build something. - WHEN the user checks out the system branch called master + WHEN the user clones definitions THEN morph build the system systems/test-system.morph of the branch master FINALLY the git server is shut down @@ -35,14 +34,12 @@ information, such as the documentation, C library headers and C static libraries. SCENARIO building a system only using runtime strata - GIVEN a workspace - AND a git server + GIVEN a git server The only change we need to make is to add a field to the system morphology to select which artifact to use in the system. AND system systems/test-system.morph uses core-runtime from core - WHEN the user checks out the system branch called master The best way to test that only using some stratum artifacts works is to check which files the output has, so we deploy a tarball and inspect @@ -52,7 +49,8 @@ its contents. AND a system in cluster test-cluster.morph in branch master called test-system AND system test-system in cluster test-cluster.morph in branch master builds systems/test-system.morph AND system test-system in cluster test-cluster.morph in branch master has deployment type: tar - WHEN the user builds the system systems/test-system.morph in branch master + WHEN the user clones definitions + AND the user builds the system systems/test-system.morph in branch master AND the user attempts to deploy the cluster test-cluster.morph in branch master with options test-system.location="$DATADIR/test.tar" The -runtime artifacts include executables and shared libraries. @@ -73,8 +71,7 @@ to go into our system, such that there are chunk artifacts that are not needed, then they don't get built. SCENARIO building a system that has unused chunks - GIVEN a workspace - AND a git server + GIVEN a git server This GIVEN has a chunk in the stratum that never successfully builds, so we know that if the system successfully builds, then we only built @@ -82,7 +79,7 @@ chunks that were needed. AND stratum strata/core.morph has chunks that aren't used in core-minimal AND system systems/test-system.morph uses core-minimal from core - WHEN the user checks out the system branch called master + WHEN the user clones definitions THEN morph build the system systems/test-system.morph of the branch master FINALLY the git server is shut down |