bringup/teardown around every test.
Brought to you by:
wtanksle
The __CUT_BRINGUP/__CUT_TEARDOWN funcions would be more useful, if they were ran around each test. That way they could be used to set up a clean environment for each test and clean it up afterwards.
The current way every test function must clean up after itself (or at the begining clean up after the previous), which makes things a little more complicated.
Note, that C++, Java, Python etc. unit-test tools do run their setUp and tearDown methods around each test.