tests: clarify the subplot to explain the steps

1 files changed, 28 insertions, 0 deletions

diff --git a/vmadm.md b/vmadm.md
index aa3a704..bfd09b4 100644
--- a/vmadm.md
+++ b/vmadm.md
@@ -142,6 +142,8 @@ that the user can log into it as root via SSH after it has booted.
 This requires that the environment it set up so that virtual machines
 can be addressed by name.
 
+First some setup.
+
 ~~~scenario
 given an installed vmadm
 given a Debian 10 OpenStack cloud image
@@ -152,6 +154,11 @@ given file .ssh/id_rsa from ssh_key
 given file .ssh/id_rsa.pub from ssh_key_pub
 given file .ssh/config from ssh_config
 given file .ssh/known_hosts from known_hosts
+~~~
+
+Then we create the VM, and verify that we can log in.
+
+~~~
 when I invoke vmadm new --config config.yaml smoke.yaml
 when I invoke ssh -F .ssh/config debian@smoke hostname
 then stdout contains "smoke"
@@ -159,9 +166,30 @@ when I invoke ssh -F .ssh/config debian@smoke df -h /
 then stdout contains "4.9G"
 when I invoke ssh -F .ssh/config debian@smoke free -m
 then stdout contains "1997"
+~~~
+
+Then we shut it down, twice. The second time is to verify shutting
+down works even if the VM is already shut down.
+
+~~~
+when I invoke vmadm shutdown --config config.yaml smoke.yaml
 when I invoke vmadm shutdown --config config.yaml smoke.yaml
+~~~
+
+Then we start it back up again and verify we can log in. Then we start
+it again, while it's already running, to verify that that works.
+
+~~~
 when I invoke vmadm start --config config.yaml smoke.yaml
 when I invoke ssh -F .ssh/config debian@smoke hostname
+when I invoke vmadm start --config config.yaml smoke.yaml
+~~~
+
+Finally, we delete it twice.
+
+~~~
+when I invoke vmadm delete --config config.yaml smoke.yaml
+when I invoke vmadm delete --config config.yaml smoke.yaml
 ~~~