Ha, I thought EasyMock was alreay a framework of choice. As that's not the case, I'm going to give Mockito a try and convert camel-jaxb tests. If all goes well I'll get back with a patch after the weekend.
Thanks, Pavel On Sat, Jan 9, 2010 at 7:48 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > On Fri, Jan 8, 2010 at 7:38 PM, Stephen Gargan <steve.gar...@gmail.com> > wrote: > > Pavel, > > > > Mock Frameworks are a subjective kind of thing, but I've had a lot of > > luck with Mockito. It's DSL (And we're fans of good DSLs round here ;) > > ) is really clean and succinct and the Argument Capture I've found > > indispensible. > > > > http://www.mockito.org/ > > > > I have heard good things about Mockito too as well. > However we do not use EasyMock that much in testing Camel. So its not > a big deal to upgrade to include both of them. > And maybe migrate to Mockito and start using it more :) > > > > > And I've also found Mycila very useful for injecting mocks into spring > > contexts, it will work with easymock too if you prefer > > > > http://code.google.com/p/mycila/wiki/MycilaTesting > > > > checkit. > > > > ste > > > > > > > > On Fri, Jan 8, 2010 at 7:47 AM, Willem Jiang <willem.ji...@gmail.com> > wrote: > >> Hi Pavel, > >> > >> We need to do the change 1, 2 at the same time. > >> My old patch can't deal with this situation > >> > >> from("direct:getJAXBElementValue") > >> .unmarshal(new > >> JaxbDataFormat("org.apache.camel.foo.bar")) > >> .to("mock:result"); > >> > >> It's very late for my time, I will work on it tomorrow. > >> > >> Willem > ...
