It is there somewhat more akin to an anteater test. Therefore, given these facts, I propose to leave the CocoonBeanTestCase disabled, and simply remove the test suite (as it isn't needed anyway.). I will continue to use the test case locally on my own testing, and will reflect on a better place for it (or some equivalent) within the build process, perhaps alongside the anteater tests.
+1. I am also worried about the time it takes to run the CocoonBeanTestCase. We already run the unit tests all too seldom, and if they take a long time, nobody will ever want to run them more often.
Ugo
