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
I think that changing the current behavior of SetupTest/AfterTest/BeforeTest may (and will) lead to some unpredictable problems. So if someone really needs hooks to set something up in the subtest lifecycle, it's better to add new types with interfaces like SetupSubTest, AfterSubTest, BeforeSubTest.
At the same time, I don't get how it may be profitable.
I've set up a suite for my tests. However, I'm having trouble using the set up and tear down features when using table tests. Is this by design?
When I run the
TestUnitTestSuite
I get the following output:Note that
setup
andbefore test
appear only once in the output even though there are two tests being run.Is there a way for me to automatically run
SetupTest
(or some alternative) prior to each of my table tests?The text was updated successfully, but these errors were encountered: