Test fixtures' teardown methods are currently executed as part the UnitTestEnvironment destructor, potentially resulting in a loss of exception infos: when an exception is thrown during teardown, the stack is unwinded before throwing. However, in case of additional exception being thrown by an unwind destructor, the program is terminated right away with the current backtrace.

As a result, the original teardown exception is going to be hidden, making debug extremely difficult.

Following the pattern implemented by googletest::UnitTest, the teardown should be executed as part of Test::run .