Mariano Martinez Peck wrote:
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).
You need to build and provide both types of images. The developer then decides which one they need based on whether or not they expect to be modifying "base" code. For example, if I'm just writing a Seaside app. that does not change Seaside itself, I would not want the Seaside tests around. It may be wise to have my build server load and run them, and let me know of test failures - but, the day to day development image should not have them. If however, when building my app., I found I was modifying and extending Seaside itself, then I would choose to use a base image that included the Seaside tests. In order to keep a build time under 10 minutes, as things scale, you need to build and test the pieces individually. Then you start your development from a known and tested baseline image. BTW, the Hudson build stuff I just announced, has this build/test scenario in mind. The "product" itself is built and saved. Then the test packages are added, and the test cases are run. Unfortunately, when the test cases are in the same package, they cannot be left out of the "product" image. In the Pier build example, some addon packages which included tests are loaded in the test build. It's not right, because the product image is missing these addon packages. There's a test package dependency chain, that could not be solved, because the tests and code were in the same package. -- Yanni Chiu