Ok, that's the big questions. Until now, the Dev image only cointained the tests of the PharoCore image. Actually, it also included the tests fro those projects where the test were in the same package (for example, RoelTyer). Now, with the new Metacello infrastructure, you will be able to take a PharoCore and evaluate:
(ConfigurationOfPharo project version: '10496') load��� (which it will load the defualt stuff, in this case, all the stuff for a dev image)
�� �
�or
(ConfigurationOfPharo project version: '10496') load: 'StandardDevImageWithTests'
which will loads not only all the packages, but also ALL the test of all packages (all packages that have tests).
So, my question is, should the test be included in the default dev image?
I think that yes, because of the following:
1) Tests are useful for documentation
2) It encourages people to run the tests before committing something (that may break something)
3) You can see the state of the image you are using.
4) Because they are not bad
5) Because if you don't want to load the test, just add a simple� 'StandardDevImageWithoutTests' after the load.
6) I don't think they take a lot of size in an image. In addition, it is a DEV image, not production. In production is logic that you don't want the tests and that may be even done with something similar to ScriptLoader >> cleanUpForProduction
So..what do you think ?
Cheers
Mariano