Peter: The way things are currently setup works fine for the production of a version block - but it's no optimal for the generation of a suite of test blocks. One approach could be enable the declaration of a block output filename.
But aside from this - there is also the question about unit test deployment logic. Currently the merlin-unit system deploys relative to build target you will end up in the situation of having to deploy all scenario together per unit-test test method (which is really painful). The underlying problem here is that Ant JUnit test-suite is kind of simplistic about the handling of test suites that have a common context - but coming up with something better involves updates to Ant's JUnit stuff - or cutting something ourselves (even approach being non-trivial). Cheers, Steve. > -----Original Message----- > From: Peter Neubauer [mailto:[EMAIL PROTECTED] > Sent: 03 September 2004 18:07 > To: [EMAIL PROTECTED] > Subject: Multiple MerlinTestCases in one project? > > Hi, > thinking about our project layout, I realize that it is only possible to > have > one block generated by the build.xml per project, and there is only one > melrin.properties that gets copied with its deployment directive > hardcoded. > > How do you manage multiple MerlinUnit TestCases where you want to test > with > different blocks, like test for wrong configurations, wrong deps etc? The > blocks could be generated in other projects as the only artifact, but: > - how do I reference them in the TestCase? I could include them as deps in > the > project of course but then only one block is generated again > - I think it would be good to be able to override the merlin.deployment > from > within the testcase in order to be able to specify a block from there, but > maybe it would be better to specify an artifact where the block should be > taken from, like the block generating sub project outcomes? > > > If nothing works, you can only have one Merlin integration test that uses > magic-generated block definitions, which I think is not good. That would > lead > to hand-coded blocks like in the merlin-unit source which will not work > once > you start versioning. > > Just random thoughts. > > /peter > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
