Recurring fails on windows tests and the recent CentOS failure

[Ian Booth]

+100

And if the only reason for embedding a suite is to use a helper type function
that does not require that suite's setup/teardown, then it really should be
factored out as a standalone function to be shared.

On 16/07/15 10:46, Tim Penhey wrote:
> I'm in agreement with Bogdan, Roger and William on this one.
> 
> If your test suite is composed of other suites, and you override the
> default setup or teardown of either the suite or the test, you MUST call
> the respective methods of the embedded suites.
> 
> Roger, if it is easy to write some code to assert this, I would LOVE to
> have that as a test. It is not something I have the ability to write
> quickly (if at all).
> 
> As a rule, you should call the setups in the order you define them in
> the struct, and call teardown in the reverse order.
> 
> Thanks,
> Tim
>