-- chris bartling --
You received this message because you are subscribed to the Google Groups "mockito" group.
To post to this group, send email to moc...@googlegroups.com.
To unsubscribe from this group, send email to mockito+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/mockito?hl=en.
The other possibility is to use setters if they're there, otherwise
use the fields directly.
On Mar 19, 11:40 am, Chris Bartling <chris.bartl...@gmail.com> wrote:
> I'm favoring reflection-based DI behavior myself. We use Spring and its
> annotations, using @Autowired and @Resource on the collaborator fields and
> never writing setters. Certainly cleans up the code and its quite obvious
> what my collaborators are. I don't know about the argument regarding OO.
> I'm of the opinion that new language features and languages are helping to
> reduce code noise. Incidentally, Groovy removes you from even writing
> setters and getters these days. I personally like the reflection-based DI
> that @InjectMocks provides. Perhaps in future versions it could be
> -- chris --
> On Fri, Mar 19, 2010 at 4:27 AM, szczepiq <szcze...@gmail.com> wrote:
> > Well spotted! I think it makes sense what you guys are saying.
> > Any other opinions?
> > Cheers,
> > Szczepan Faber
> >> .
> >> For more options, visit this group at
> > --
> > You received this message because you are subscribed to the Google Groups
> > "mockito" group.
> > To post to this group, send email to moc...@googlegroups.com.
> > To unsubscribe from this group, send email to
Another way to inject annotated attributes in tests is the EasyGloss Library:
EasyGloss doesn't do any mock creation, just injection.
This gives you the freedom to choose what to inject.