|
From: Bordet, S. <Sim...@co...> - 2002-01-30 16:20:52
|
<flamemode> Ok, JUnit really sucks. REALLY. Apart for very simple stuff, it is really not good. So I thought, ok, should be extensible, and went to take a look at the = code. My god, a mess, a real mess. These XP and pattern experts (Beck and Gamma) did an awful job. You can find in Javadocs: "Parts of this method was written at 2337 meters in the H=FCffih=FCtte, = Kanton Uri". Hey, Switzerland is beautiful, but this one burned his brain at that = altitude, and wrote crappy stuff. Has anyone tried to write tests so that some initialization code is run = once per test class in an easy way (and please don't talk to me about = TestSetup, another crappy thing) ? This is only one of the missing pieces. Wanna take a look to a bad design ? Interface Test depends on class TestResult, ok this far.=20 Test should be the main interface for tests: wanna write a fully custom = test ? just implement it.=20 You cannot, because TestResult depends on a subclass of Test, TestCase = :( And no separation between what the user implements and framework classes = that run that implementation. Sooner or later, I will replace it. Hurts me. </flamemode> :) Simon |