Jim Cheesman wrote:
>
> >
> >I'm not yet sure how it would be possible to take a particular test and
> >switch it among the three forms (in-container, mock object, functional) by
> >setting a switch; nor am I sure that I understand the main rationale for
> >doing so.
>
> 1. I think a large part of the rationale is that people don't necessarily
> distinguish between unit, black-box, functional etc. etc. etc. testing.
> They just want to test the code. (And the difference between the various
> types is often hazy at best...)
and as we all know, testing is quite often "squeezed" at during a
project. Anything that makes performing tests easier is a winner as far
as i'm concerned - that must be why junit has taken off. It makes it
easy to write and maintain unit tests, so unit tests are more likely to
be used.
>
> 2. Much of the testing is complementary, and an integrated test suite where
> the same test class, with the same import statements, did all the testing
> for one servlet would be tidy. (Yes, I know you can do this at the moment
> but I wouldn't call the packages in any way "integrated". Couple this with
> some easy to understand doco and...
>
> 3. If management asks "How are you testing?" it's nice to be able to point
> to one thing and say "with this"... ;)
>
quite, don't underestimate the "dilbert" factor of describing to
management what you're doing....
and don't underestimate the power of having an open source test suite
that has good docs, is easy to use, and can be used to perform all sorts
of tests on a web application- using one toolset rather than 4 or 5 is
definitely easier to get started with.
Jari
--
Jari Worsley
Senior Programmer
Hyperlink Interactive Ltd
