You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hivemind.apache.org by "Howard M. Lewis Ship" <hl...@comcast.net> on 2004/06/21 17:53:47 UTC
Some pudding (as in, "the proof is in the ...")
I'm actually beginning to shift focus away from HiveMind and back to Tapestry.
I'm seeing, in my own work, exactly what I've been preaching: easy, useful tests.
The work I'm doing is to prise apart some monolithic classes and turn them into collaborating
services.
I'm using many small, focused services. I use JUnit tests and mock objects (i.e., www.easymock.org)
to test each service in isolation. Usually, just one or two tests, since there are so few code paths
to be concerned about.
I think add an "integration" test, that builds a Registry (incorporating Tapestry's hivemodule.sdl)
and check that I can perform work there; this is important to ensure that there are no errors in the
MDD.
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-dev-help@jakarta.apache.org