There are a few of these libraries to make running Guice in JUnit easier, Onami is another: http://onami.apache.org/test/
However, if you have to add all of this extra stuff to your unit test, is it really worth it? Still struggling with all of this... but starting to hone in on my project's best practices. Bill- On Mon, Jul 1, 2013 at 12:44 PM, uwe schaefer <u...@codesmell.de> wrote: > On 06/29/2013 03:13 PM, William Speirs wrote: > > I'm strongly leaning towards the best practice of: If you're having to >> create an injector in your unit test, then you're doing it wrong. >> > > maybe it makes it worse in your perspective, but yuo might want to have a > look at jukito. > > https://code.google.com/p/**jukito/ <https://code.google.com/p/jukito/> > > at least it makes it easy to combine mockito&guice > > cu uwe > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@wicket.**apache.org<users-unsubscr...@wicket.apache.org> > For additional commands, e-mail: users-h...@wicket.apache.org > >
