diff options
Diffstat (limited to 'vmdb2.md')
| -rw-r--r-- | vmdb2.md | 19 |
1 files changed, 16 insertions, 3 deletions
@@ -258,6 +258,7 @@ kind of testing, and that the teardown field in the step is implemented by the echo step. It's not a generic feature. ~~~scenario +given an installed vmdb2 given file happy.vmdb when I run vmdb2 -v happy.vmdb --output=happy.img then exit code is 0 @@ -272,6 +273,18 @@ steps: teardown: bar_teardown ~~~ +## Checking the version + +_Requirement: We can ask vmdb2 for its version._ + + +~~~scenario +given an installed vmdb2 +when I run vmdb2 --version +then exit code is 0 +then stdout matches regex ^\d+\.\d+$ +~~~ + ## Jinja2 templating in specification file values @@ -283,6 +296,7 @@ outputs the image file name given by the user. A more realistic specification file would instead do thing like create the file. ~~~scenario +given an installed vmdb2 given file j2.vmdb when I run vmdb2 -v j2.vmdb --output=foo.img then exit code is 0 @@ -303,6 +317,7 @@ in the right order then? This scenario uses the "error" step provided for testing this kind of thing. ~~~scenario +given an installed vmdb2 given file unhappy.vmdb when I try to run vmdb2 -v unhappy.vmdb --output=unhappy.img then exit code is 1 @@ -310,7 +325,7 @@ then stdout contains "foo\nyikes\n" then stdout contains "WAT?!\n" then stdout contains "foo_teardown\n" then stdout doesn't contain "bar_step" -then stdout doesn't contain "bar_teardown" +then stdout contains "bar_teardown" ~~~ ~~~{.file #unhappy.vmdb .yaml .numberLines} @@ -322,5 +337,3 @@ steps: - echo: bar teardown: bar_teardown ~~~ - - |