Berin, At work we have an AbstractPhoenixTestCase. It is basically a fake container that extends TestCase & supports the life cycle. You extend it and hand-hard code service implementations for the lifecycle process to use. It works a beaut and we called it punit. We can't donate, but would almost certainly shift to a clean-room Apache written equivalent.
- Paul >>From the thread entitled: >"[junit] Unit testing multithreaded network code" > >(which by the way is an interesting read for testing networking code) > >Had the opinions posted from two developers: > >"The general issue of how to approach this sort of issue remains >unsolved, but I sidestepped my own problem by passing the >responsibilty of verifying the robustness of code to the Jakarta >Avalon project. I may be taking the lazy way out, but I trust the >Apache people to write working software." > > From: weitzman_d [mailto:[EMAIL PROTECTED]] > >The response was: > >"This might be a deceiving attitude at best. The Avalon project has a >high >code quality indeed, but as for Jakarta projects in general this does >not hold. >Just look randomly around and you'll find lots and lots and lots of >really >bad code with zero tests with no regard to object-oriented principles >and >which violates almost any heuristics for good code I know of." > > From: Johannes Link [mailto:[EMAIL PROTECTED]] > > >I think we have a reputation for quality--which I would like to see >continue. > > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
