Currently TestCase is tied to the ECM very tightly. The configuration information and the contianer are guaranteed to be the ECM. There is no way to really adjust the system to use other components easily.
I would like to have such a system. I would like to have a TestCase project that will load up the container with all the components needed for your tests, and then perform the testing.
I also would like to have a container testing suite, but that would be a bit more complicated.
The bottom line of what I would like to see is the inclusion of an ANT task that points to the proper configuration files and the JAR files for the container. What would *really* be good is to test one component against all the available containers (at least at the embedded container level).
Unfortunately this is a lot of work to try and attempt for the immediate future. Another challenge we have to overcome is the components that *depend* on TestCase as its own entity. That would make them depend directly on ECM just to test the component--which happens indirectly now anyway.
Do we merge the two?
(I think it is safe to count Steve as a +1 ;P)
+1 from me--I don't feel like writing up all the docs that
Steve would like to see, and we need to get past the
releases. :)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
