El mié, 06-01-2010 a las 16:56 -0200, csrabak@bol.com.br escribió:
Alexandre,
Once upon a time I thought like you, but I changed my mind when I realized that more and more the tests are being engineered in such a fashion that using them for the sake of an example is becoming convoluted.
As we create all the machinery (setup and tear down) to do Unit Tests the test itself conveys less information unless you start to navigate the SUnit land, and I feel it will become even more inexpugnable for newcomers as soon PhExample enters the scene (you might have chained tests).
Notwithstanding the accepted notion that tests are a form of documentation, I would say more and more they're falling into the same slot of the argument "you have access to the code": true but not practical for the day to day chores.
+1 I agree with you 100% but I vote for maintaining the tests in the dev image and giving the users a quick/easy/transcript ready way to unload them if they want. Also, for deploy scenarios, the intended way is to use a PharoCore image and use a personalized script (with gofer/metacello) to load only the packages needed. -- Miguel Cobá http://miguel.leugim.com.mx