Open housel opened 3 years ago
Also, there are no unit tests for suite-setup-function
and suite-cleanup-function
.
It's no secret I've been trying to reduce the need for suites, but this strikes me as the one truly useful thing about them: giving a collection of tests a shared setup/teardown. We should
To be explicit, it should be possible to define a suite with setup/teardown, plus a bunch of top-level tests, not include the suite in any parent suite, and the right thing should happen.
When the --test command-line option is used to invoke a particular test, the setup-function and cleanup-function of the suite to which it (transitively) belongs are not called.