embedding tests nearer the code

derekbrans d.brans at shaw.ca
Sat Apr 12 21:37:28 UTC 2003


checkout BrowseUnit on SqueakMap

--- In squeak at yahoogroups.com, Simon Michael <simon at j...> wrote:
> "Andreas Raab" <andreas.raab at g...> writes:
> > primary reasons why people often _don't_ write tests. To me, the 
tests
> > really should be embedded right into the method you're writing - 
making
> > extra classes, accessors and the like just gets into your way and
> > detaches the place where you find the code from the place where 
you find
> > the test. It can be tremendously hard to guess in which class 
exactly
> > you may find a test (if any) for a certain method.
> 
> I agree. I assume "embedded into the method" requires some future 
UI
> enhancement. But right now, how about putting tests in the class 
they test
> ? Category "tests". Just a small SUnit modification needed I think.



More information about the Squeak-dev mailing list