[ENH][TEST] ClassBuilder format tests

ducasse ducasse at iam.unibe.ch
Mon Jan 5 08:22:02 UTC 2004

On 4 janv. 04, at 23:24, Andreas Raab wrote:

>> No tearDown is run after each tests. I was forced to extend SUnit to
>> provide the behavior you describe because our test suite was taking
>> too much time, so I'm really sure about this behavior. In fact setUp
>> and tearDown are always run before and after each tests because they
>> control the context.
> Really? When I did it (originally and just now) I'm getting failures 
> in the
> tests. I don't know what the problem is but apparently something goes 
> wrong
> here. You can try for yourself by moving the cleanup to tearDown and 
> make
> cleanup empty.

I will.
Look at the sender of tearDown.

>> Noury started to rewrite completely the classbuilder but he got glued
>> into teaching and other less fun activities.
> Without writing tests first? That's going to be ... shall we say ...
> "interesting". The many invariants of ClassBuilder aren't well (if at 
> all)
> documented and while it isn't a large corpus of code to deal with, 
> some of
> it is VERY subtle - just look at ClassBuilder>>update:to: which has ten
> times as much comments as it has code (for good reasons).

I imagine that he started to write tests, noury had to fix several tims 
the class builder
for metaclasstalk

> Cheers,
>   - Andreas

More information about the Squeak-dev mailing list