| Subject: | alternative to AutoskipFailedSetup() |
A 'setup' test seems to be useful for things that need to be ran repeatedly before each test, yet I think it is more common to need to run one or more one-time setup operations. Given that, it would be convenient to be able to specify, on an individual test basis, whether a failure of that test should result in the entire test suite being skipped or aborted.
AutoskipFailedSetup() isn't ideal here, as you might not be using a 'setup' test, or you may wish the entire suite to return failures rather than skips.
Additional hash keys in the test specification could address this:
OnFailureSkipNext => 1, # optional prerequisite for the next test not met
OnFailureSkipAll => 1, # optional prerequisite for this suite not met
OnFailureFailAll => 1, # mandatory prerequisite for this suite not met
etc.
-Tom