El lun, 19-10-2009 a las 18:14 +0200, Lukas Renggli escribió: > >> Personally I would like to download an image *without* any tests, no > >> matter if this is a core or a dev image. And have included a detailed > >> report on the results of running all the tests in that particular > >> image. > > > > But why, apart from the tiny image disk usage reduction. The test > > sometimes show how to use the, most times underdocumented, package. > > IMHO, that's a myth. Did a single test case ever in your entire life > help you to understand a piece of code? It never happened to me so far > :-) > > The rational behind my opinion is that I do not care about the tests > of the other packages when I develop software. Did you ever (other > than by accident) run the Collection or Compiler tests when you > developed some of your code? > > Btw, the same is true for the Monticello working copies. I frankly do > not care what version of Collection or Compiler is loaded in my image. > Sometimes I just drop all this information before I load my code. This > greatly reduces clutter.
I agree. But then maybe is better to use the other alternative proposed of putting a visible one-liner or one-click to unload the tests after downloading and let the user unload them on demand in images used for deployment and not in images used for everyday work. Respect to the Monticello working copies I fully agree. > > Lukas > -- Miguel Cobá http://miguel.leugim.com.mx _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
