Stéphane Ducasse wrote: > On Feb 10, 2009, at 10:33 AM, Michael Rueger 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. > > but if Collections-Kernel-Tests is a package then it will not be stored.
Its contents will be stored in Collections-Kernel because of the way Monticello defines package contents by name matching. > Then why having tests close to the code is a problem > I could do > > Collections-Kernel dropTests > et voila! It might be just my personal work style/habit, but if I'm "using" a package I don't want to have the tests in my work environment. Less stuff, less clutter, less distraction. Also searching for senders etc is made harder because of all the usages in test classes show up as well. Michael _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
