Unfortunately, for unit testing, we only have an AbstractCompositeTestCase which extends ExcaliburTestCase, which implements Composable and not Serviceable, right?euh... wrong I think. The ExcaliburTestCase creates an ECM, and the ECM supports both Composable and Serviceable. Or what problem do you see?
I only see my ignorance regarding Avalon, ECM, etc. ;-). Thanks for clarifying the issue.
Maybe it would be easier if you ran the tests from inside a running Cocoon (possibly using the CocoonBean), so that the whole environment is created. But maybe that goes against the spirit of unit tests?
I'm afraid that starting Cocoon every time you want to run a test might take so much time that you'd end up not running them at all. Or at least, you'd end up running the full test suite before releasing something, which is perfectly fine, but is not what Test Driven Development is all about. I want my tests to drive coding: write a test, see it fail (red bar), fix the code, green bar, refactor, green bar (hopefully), and so on...
Ugo
