Add global setup/teardown
To make things simpler and avoid boilerplate/copy-pasting, scruf should support global setup/teardowns. For example, a common use case would be for testing a program with some extra variables (either for convenience, or test interaction with environment variables). In cram, since all tests in a file are run within the same shell session this could be acheived with having your file start with something like:
$ alias my-prg=$TESTDIR/my-prg
$ export var_to_reuse="some value"
$ export USEFUL_ENV_VAR=123
While much of this could be accomplished using env vars with scruf, having a dedicated setup would be a definite improvement, as well it not being possible to scope env vars at the file-level.
Combining with #8 this could probably be achieved by allowing [SETUP]
calls at the start of files (and potentially removing their usage at a test-level)