> > I think users will find samples on how to test controls very valuable. > However, as Ken pointed out, most control tests require a container. >
I don't fully agree with this. I think it is possible to provide a 'mock' container, in fact some of existing tests do exactly this. Things like resource scope, external configuration, and other container services can be mocked and provided by a test harness, that makes it possible to examine how a control behaves w/out necessarily requiring a you run w/in an actual server environment. A lot of it is a function of the control and the contextual services it uses to do its job. For example, a control could be written to run in the web tier and have a dependency on a ServletContext contextual service... you can certainly mock this too, but now the effort to create the simulated runtime environment has gone up. The more services the control uses, the more effort exists to create a simulation of the environment it needs.
