refactor(subplot.{md,yaml}): rename step to check for success

The old step "then program finished successfully" comes originally
from runcmd.yaml. For lib/runcmd.yaml it has been replaced with "then
command is successful".

Change all uses of the old wording to the new one. Don't use
lib/runcmd.yaml yet, but keep the binding subplot.yaml to bind the new
wording to the function from lib/runcmd.py (which it did before
already, so no change).

1 files changed, 15 insertions, 15 deletions

diff --git a/subplot.md b/subplot.md
index 8ff048e..7e32ea2 100644
--- a/subplot.md
+++ b/subplot.md
@@ -672,7 +672,7 @@ then scenario "Simple" was run
 and step "given precondition foo" was run
 and step "when I do bar" was run
 and step "then bar was done" was run
-and program finished successfully
+and command is successful
 ~~~
 
 
@@ -697,7 +697,7 @@ then scenario "All keywords" was run
 and step "given precondition foo" was run
 and step "when I do bar" was run
 and step "then bar was done" was run
-and program finished successfully
+and command is successful
 ~~~
 
 ~~~{#allkeywords.md .file .markdown .numberLines}
@@ -732,7 +732,7 @@ and file aliases.html matches regex /when<[^>]*> I do bar/
 and file aliases.html matches regex /and<[^>]*> I do foobar/
 and file aliases.html matches regex /then<[^>]*> bar was done/
 and file aliases.html matches regex /but<[^>]*> foobar was done/
-and program finished successfully
+and command is successful
 ~~~
 
 ~~~{#aliases.md .file .markdown .numberLines}
@@ -807,7 +807,7 @@ then scenario "Simple" was run
 and step "given precondition foo" was run
 and step "when I do bar" was run
 and step "then bar was done" was run
-and program finished successfully
+and command is successful
 ~~~
 
 ~~~~{#emptylines.md .file .markdown .numberLines}
@@ -897,7 +897,7 @@ when I run sp-codegen --run cleanup-success-python.md -o test.py
 then scenario "Cleanup" was run
 and step "given foo" was run, and then step "given bar"
 and cleanup for "given bar" was run, and then for "given foo"
-and program finished successfully
+and command is successful
 ~~~
 
 
@@ -960,7 +960,7 @@ when I run sp-codegen --run cleanup-success-bash.md -o test.sh
 then scenario "Cleanup" was run
 and step "given foo" was run, and then step "given bar"
 and cleanup for "given bar" was run, and then for "given foo"
-and program finished successfully
+and command is successful
 ~~~
 
 ~~~~~{#cleanup-success-bash.md .file .markdown .numberLines}
@@ -1032,7 +1032,7 @@ when I run sp-codegen --run simplepattern.md -o test.py
 then scenario "Simple pattern" was run
 and step "given I am Tomjon" was run
 and output matches /function got argument name as Tomjon/
-and program finished successfully
+and command is successful
 ~~~
 
 ~~~~{#simplepattern.md .file .markdown .numberLines}
@@ -1101,7 +1101,7 @@ given file confusedbutok.md
 and file confusedbutok.yaml
 and file capture.py
 when I run sp-codegen --run confusedbutok.md -o test.py
-then program finished successfully
+then command is successful
 ~~~
 
 ~~~~{#confusedbutok.md .file .markdown .numberLines}
@@ -1134,7 +1134,7 @@ when I run sp-codegen --run regex.md -o test.py
 then scenario "Regex" was run
 and step "given I am Tomjon" was run
 and output matches /function got argument name as Tomjon/
-and program finished successfully
+and command is successful
 ~~~
 
 ~~~~{#regex.md .file .markdown .numberLines}
@@ -1238,7 +1238,7 @@ and file b.yaml
 and file f.py
 when I run sp-codegen --run scenarioislowest.md -o test.py
 then scenario "heading 1.1.1" was run
-and program finished successfully
+and command is successful
 ~~~
 
 ~~~~{#scenarioislowest.md .file .markdown .numberLines}
@@ -1266,7 +1266,7 @@ and file b.yaml
 and file f.py
 when I run sp-codegen --run subisnotnewscenario.md -o test.py
 then scenario "heading 1.1a" was run
-and program finished successfully
+and command is successful
 ~~~
 
 ~~~~{#subisnotnewscenario.md .file .markdown .numberLines}
@@ -1298,7 +1298,7 @@ and file f.py
 when I run sp-codegen --run samelevelisnewscenario.md -o test.py
 then scenario "heading 1.1.1" was run
 and scenario "heading 1.1.2" was run
-and program finished successfully
+and command is successful
 ~~~
 
 ~~~~{#samelevelisnewscenario.md .file .markdown .numberLines}
@@ -1333,7 +1333,7 @@ and file f.py
 when I run sp-codegen --run higherisnewscenario.md -o test.py
 then scenario "heading 1.1.1" was run
 and scenario "heading 1.2" was run
-and program finished successfully
+and command is successful
 ~~~
 
 ~~~~{#higherisnewscenario.md .file .markdown .numberLines}
@@ -1421,7 +1421,7 @@ when I run sp-codegen twoscenarios-python.md -o test.py
 and I run python3 test.py on
 then scenario "One" was run
 and scenario "Two" was not run
-and program finished successfully
+and command is successful
 ~~~
 
 ~~~{#twoscenarios-python.md .file .markdown .numberLines}
@@ -1461,7 +1461,7 @@ when I run sp-codegen twoscenarios-bash.md -o test.sh
 and I run bash test.sh on
 then scenario "One" was run
 and scenario "Two" was not run
-and program finished successfully
+and command is successful
 ~~~