You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
fix the above problem
explicitly document the use of suites for shared setup/teardown
make sure there's no warning for suites that aren't used or exported
make sure the current auto-generated suite includes the explicit suite rather than directly including the tests it contains. (I think this works but need to verify.)
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.
The text was updated successfully, but these errors were encountered: