I'm working with a client who're using Spring extensively. When I look at
their Unit Test code I realize that I'm looking at a heap
of integration tests and not real Unit Tests. In part it seems to come from
the autowiring of Spring. In addition I've been told that creating new
contexts on the fly in Spring can (in their case) really slow the running of
the unit tests.

I realize that we can bypass Spring completely but the point was made that
in that case we're testing without the Spring Security Context and other
rules, which means we're not really testing how the code behaves in real
life.

I'm wondering if any one has good writing on Unit Testing with Spring so I
can get my head wrapped around what it looks when its done well?

Cheers
Mark Levison

[image: Mark] <http://www.flickr.com/photos/36331075@N00/3833840021/>*Mark
Levison* | Agile Pain Relief Consulting <http://agilepainrelief.com/> |
Certified Scrum Trainer
Agile Editor @ InfoQ <http://www.infoq.com/about.jsp> |
Blog<http://www.notesfromatooluser.com/>|
Twitter <http://twitter.com/mlevison> | Office: (613) 862-2538
Recent Entries: Story Slicing How Small is Small
Enough<http://agilepainrelief.com/notesfromatooluser/2010/09/story-slicing-how-s\
mall-is-enough.html>,
Why use an Agile
Coach<http://www.notesfromatooluser.com/2009/11/why-use-an-agile-coach.html>


[Non-text portions of this message have been removed]