It is more for having examples under hands. Cheers, Alexandre
On 6 Jan 2010, at 13:29, Yanni Chiu wrote: > Alexandre Bergel wrote: >>> For example, if I'm just writing a Seaside app. that does not change >>> Seaside itself, I would not want the Seaside tests around. >> >> >> I have a different opinion > > Okay, Seaside was just one example package I chose for illustration. > Perhaps it was not the best choice, since I said I was building a > Seaside application. What about Collections tests or Morphic tests? > > Also, not having them around, doesn't mean never running them. They > could be run by a build process, and I would be told if they failed. > Meanwhile, I would never be distracted by their presence. I would not > have to think about which SUnit tests to run; I would just run all the > ones in my image. > > -- > Yanni > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
