26 Nov
2009
26 Nov
'09
2:58 p.m.
On 25 nov. 2009, at 15:07, Dale Henrichs wrote:
Simon,
Another alternative would be to import the tests that you're
interested in into ConfigurationOfMoose:
spec
project: 'MooseAlgos Tests'
copyFrom: 'MooseAlgos for Moose'
with: [ spec loads: 'Tests' ].
This is similar to what you are doing with option two, with the
twist that you only need ConfigurationOfMoose loaded to be able to
access tests...
Indeed, an interesting alternative. It depends on how I want to run my
tests. Maybe I would like a separate report for each Configuration, I
have to play with Metacello by myself.
Dale
----- "Simon Denier" <simon.denier(a)inria.fr> wrote:
| Hi there
|
| Now with a few weeks of running, I have settled about a new use case
|
| for the test server.
|
| This is issue 226 in the bug tracker of Moose.
|
| Basically we now have multiple ConfigurationOf... to manage our
| projects, and 'Tests' groups within those projects to identify
| packages for testing.
|
| Right now my test server only loads ConfigurationOfMoose, triggering
|
| the loading of all other Configuration.
|
| ...but...
|
| It only retrieves the Tests group of ConfigurationOfMoose, which
means
|
| that tests defined in other configurations are not run. Now of
course,
|
| I want to run those too.
|
| I can think of two solutions:
| 1) either Metacello makes the transivite closure on groups, which
| means it merges groups from different projects bearing the same
name.
| 2) either I explicitly declare in my test server all configurations
| for which I want to run the tests.
| TestProject withAll: {ConfigurationOfMondrian.
ConfigurationOfGlamour.
|
| ConfigurationOfMoose}
|
| The first solution is more elegant, but keeping in line with my idea
|
| that test requirements should be explicit, I think I will go with
the
|
| second. The idea is that you should state which projects you want to
|
| test, and you dont want to run tests for all projects/configurations
|
| you depend on.
|
| Now, what do you think?
|
| --
| Simon
--
Simon