Alexandre Bergel wrote: >> nonono ;-) >> See earlier mails in this thread, this way you end up with the tests >> stored in the core package because e.g. Collections-Kernel also >> matches Collections-Kernel-Tests. > > Is it a bad thing? > > <beReadyToShot> > To that extend, I was wondering why we have the TestCase class. > Ideally, I would like to have all the test methods coming along with > the domain. As I have for documentation and comment. When I browse > Lukas' code, the complete class hierarchy in the domain is duplicated > in the tests. When we wrote the tests of the collection, we duplicated > even method categories! > With all that said, feel free to shot :-) > </beReadyToShot >
For "normal" development work the test code "pollutes" the work environment IMHO. It also would make it harder to deploy applications where you want to strip out the test code (or not load it in the first place). Michael _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
