> > I have a test case (for me almost the only way to get > things tested in > > the first place), but you cannot use it as a testcase in > turbine, since > > I adjusted the turbine sources, to get it fixed > independetly of turbine > > in the first place ;). (turbine 2 is lacking a lot of tests > anyway..) > > Any tips on getting this running in a test without > stripping out calls > > to the eg TurbinResources (besides from running Turbine itself..) > > You can start turbine from a unit test using TurbineConfig, > or use mock > objects. It may be that a test is not necessary, especially if someone > who is using turbine 2 and can confirm the changes is willing > to do the > commit.
Or you can create an integration unit test. Extend ServletTestCase and use cactus to perform an in-container test with t2. I'd like to echo James comment, unit tests will always help understanding and getting patches looked at faster. ================================================================= Jeffrey D. Brekke Quad/Graphics [EMAIL PROTECTED] http://www.qg.com -- 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]>
