Ken Tam wrote:
A mock container is still a container :) My point here was that addingI see now what you're saying about JUnit. By itself it really won't do much for Control testing.
"plain junit" support to the basic controls build project doesn't add a
ton of value (if you know junit, just add it yourself), and that adding
any kind of container-based tests (mock or otherwise) adds a bunch of
complexity that I'm also not convinced belongs in a basic build.
Personally, as a developer when I look at a new technology, the lower
the apparent initial barrier to entry the more likely I am to dig
deeper.
Also, I think part of creating a lower entry barrier is making it easy to write tests. Testing, however, plays a central part in my development.
Note that a number of ppl have expressed interest in building a
junit-based container for controls + associated build infrastructure.
I'll be more than happy to review and submit any work people want to do
in this area.
Great! I'll take a look and try to bang out some code for this then... Thanks,
- Dan
-- Dan Diephouse Envoi Solutions LLC http://envoisolutions.com/people/dan
