diff options
author | Lars Wirzenius <liw@liw.fi> | 2020-04-01 10:51:29 +0300 |
---|---|---|
committer | Lars Wirzenius <liw@liw.fi> | 2020-04-01 10:51:29 +0300 |
commit | 9d9d6e0dc296829e8c54838b4a8725db80abccdc (patch) | |
tree | 41e1c214cb7ea35e12038a9bd8d610bc1a4390e2 /contractor.md | |
parent | 03ef3e9c9fe0afd09e97871f86dab1d1f1ce0c1f (diff) | |
download | ick-contractor-9d9d6e0dc296829e8c54838b4a8725db80abccdc.tar.gz |
Add: scenario to check contractor dump for parsing build spec
Diffstat (limited to 'contractor.md')
-rw-r--r-- | contractor.md | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/contractor.md b/contractor.md index 6a6b99d..f331a7f 100644 --- a/contractor.md +++ b/contractor.md @@ -235,6 +235,25 @@ This chapter specifies acceptance criteria for the Contractor, as *scenarios*, which also define how the criteria are automatically verified. +## Local use of the Contractor + +These scenarios use the Contractor locally, to make sure it can do +things that don't require the VM. + +### Parse build spec + +Make sure the Contractor can read a build spec and dump it back out, +as JSON. This exercises the parsing code. JSON output is chosen, +instead of YAML, to make sure the program doesn't just copy input to +output. + +~~~scenario +given file hello.c +and file contractor.yaml +when I run contractor dump contractor.yaml +then the JSON output matches contractor.yaml +~~~ + ## Smoke tests These scenarios build a simple "hello, world" C application on a |