Niclas Hedhman wrote:
TCK Harness for Containers have the problems of Inversion of Control, where it
needs to invert (!) that. Perhaps there needs to be a Specification for
Container Testability. The only alternative that I can see is that the
Container provides the TCK Harness itself.
I think I stop here and see if anyone has some reflections.
One idea for testing the container is to have a Test Component, or set of test
components that excersize all the contracts from the component view point.
The TCK would provide the hook to create the container, and access the test
component. If the container failed to create the component and satisfy its
requirements then the test failed.
There would probably have to be multiple tests of this type due to the different
contracts that need to be tested.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
