On Feb 10, 2009, at 1:26 PM, Michael Rueger wrote: > 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.
Ah yes shit. I hate this pattern matching. Now can we have the same as in Seaside. I imgaine that they have several package with non matching names. > Top-(Purpose-)(Platform-)Rest > > * Seaside-Canvas contains he canvas implementation. > * Seaside-Squeak-Canvas contains the platform specific code of > the canvas implementation. > * Seaside-Examples-Canvas contains example code showing off the > canvas implementation. > * Seaside-Tests-Canvas contains the tests for the canvas > implementation. > * Seaside-Tests-Squeak-Canvas contains the platform specific > tests of the canvas implementation. > > >> 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. but then you miss the point of tests been an active documentation. Then we could really have dropTest process. Else the real pain is that we will have to synchronise tests and package and there is nothing less useful than to have tests that are not in sync with a package > > > Michael > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
