Lukas What I would like ideally is that I get a miniimage + a configuration + a **FAST** package loading so that we could load all the tests each time we integrate then we could have the tests not in the image.
I think that there are different scenarios (dev my app vs changing the system) and I can tell you that they are change like cleaning image segment for which I would love to have tests because I would be more confortable with fixing it. Stef >>> 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. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > 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
