Le 8 mars 04, à 16:45, Markus Gaelli a écrit :

> Hi Göran,
>
>> Now, *forget* my ideas. I want to hear creative good ideas from you! 
>> How
>> do we improve the quality of the standard packages? Think broad now,
>> don't only think about code conventions or class comments.
>>
>> I know for example Steph will rightly so push unit tests :) but before
>> you do that Steph - don't just say "We should all write tests!" :) Try
>> to come up with some idea, mechanism, tool or proposal that actually
>> would have a chance of *moving us* in that direction.
>
> One little thing which could have great impact on the quality of the 
> code, would
> be to use the little Object>>assert: mechanism, which is there since 
> long time,
> waiting to be used in all kinds of pre- and postconditions and 
> invariants.
>
> I did a little counting and while we have more than 1000 unit tests 
> (great) in the image
> right now we have only 23 (!) occurrences of assert: sent somewhere 
> outside a unit test.
> Romain Robbes digged out an assert: mechanism of Vassili Bykov
> http://www.smalltalkchronicles.net/edition2-1/st_compiler.htm
> which won't do any time penalty if switched off. Romain will introduce 
> that soon
> (sorry Romain, hope I did not spoil too much here ;-)
>
Not at all, I posted It just two minutes before you ;-).

Concerning unit tests, I'll try to do as much as I can with BrowseUnit.
There is a blackboard for all sorts of ideas we could implement to
ease unit testing there .

http://minnow.cc.gatech.edu/squeak/3113