Adrian Lienhard wrote:
KernelDropTests"). Michael, what would you suggest as a scheme? How about the following solution I suggested in a previous mail?
IIRC that was exactly what I suggested as well :-) So I'm all for it :-) Michael
Kernel-Numbers Kernel-Traits Kernel-Compiler ... Libraries-Collections Libraries-Regex Libraries-Network ... Tests-Kernel Tests-Libraries ...
In the class categories we could still have a fine-grained structure for tests, like
Tests-Kernel-Numbers Tests-Kernel-Traits Tests-Libraries-Collections ...
Like this we have sort of a "tests close to the code" since the last part, e.g., "Libraries-Collections" would match the category structure of the implementation. Basically it's just that we prefix the categories with "Test-" and that we have a coarse Top level structure. Stef, wouldn't that also (partly) satisfy your wish of organizing tests close to the code?
Adrian
Michael
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project