Hi Andreas,

>  Sure, one would *hope* that they add value by documenting behavior 
> but there is a) neither a guarantuee for that and b) you would equally 
> hope that all the other classes add value by documentation behavior 
> too. And then should we stop counting these too? ;-)

Romain Robbes and me are working on a five pane BrowseUnit/OmniBrowser 
combination to integrate unit tests as documentation/ link them more 
closely to code.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.tiff
Type: image/tiff
Size: 71382 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20041214/b343fc38/test.tiff
-------------- next part --------------

Note, that the test:[] block is optional to denote the method(s) under 
test.

If you want to see a prototype (including some explaining slides) see 
the image
which Oscar presented at the OOSPLA 2004 workshop "Revival of Dynamic 
Languages"

http://www.iam.unibe.ch/~gaelli/oneMethodCommandsRDL.image.gz

It also serves the concrete types of the methods under test in some 
balloon help.

The according paper "One-Method Commands: Linking Methods and Their 
Tests" is on:
http://pico.vub.ac.be/~wdmeuter/RDL04/papers/Gaelli.pdf

Cheers,

Markus