>I am pretty sure that the elegant design used in JUnit could have been refactored quickly to do what those guys wanted...
I'm not so sure. I extended JUnit last year for our functional automated test system. While I agree that JUnit is understandable using Design Patterns, I found it tougher to extend than I originally expected. From the Conclusion of A Cook's Tour:
"There is a high pattern "density" around TestCase, which is the key abstraction of JUnit. Designs with high pattern density are easier to use but harder to change."
I'm not so sure. I extended JUnit last year for our functional automated test system. While I agree that JUnit is understandable using Design Patterns, I found it tougher to extend than I originally expected. From the Conclusion of A Cook's Tour: