Re: Multiple MerlinTestCases in one project?

Niclas,
On Saturday 04 September 2004 11.41, Niclas Hedhman wrote:
> My take on this is probably the "least resistance path".
>
> Magic projects are fairly cheap, so I would organize the tesk blocks as
> their own small projects, and have the test project invoke those blocks
> through their artifact IDs.
That sounds good for now I think.

The other problem, that AbstractMerlinTestCase can't refernce or specify the 
merlin.deployment in the merlin.properties is a bigger showstopper for 
multiple testcases in one project, as you can't reference your generated 
block in the test-projects.

Will try to look in the source to solve that problem if there is no 
workaround?

/peter