@sbrannen this doesn't ask a fundamental question "why did the junit team release a version where not only were lifecycle methods for setup and teardown broken across versions, but even the fundamental names and behaviours of assert() methods.

Hadoop test based was painful enough-reinforced why the move to assertJ assertions on new tests had been the right decision. Leaving only: lifecycle, parameterisation, timeouts (still broken), and the subtle failure of how an overloaded test case must redeclare as @ Test again.

The reason everyone has stayed on v4 is the move to v5 was needlessly painful