Unit tests vs integration tests with Spring

Question

I\'m working on a Spring MVC project, and I have unit tests for all of the various components in the source tree.

For example, if I have a controller HomeContr

Answer 1

A few isolated points:

Yes, it's a common approach to Spring testing - seperate unit tests and integration tests where the former doesn't load any Spring context.

For your unit tests, maybe consider mocking to ensure that your tests are focussed on one isolated module.

If you're tests are wiring in a ton of dependencies then they aren't really unit tests. They're integration tests where you are wiring of dependencies using new rather than dependency injection. A waste of time and duplicated effort when your production application uses Spring!

Basic integration tests to bring up your Spring contexts are useful.

The @required annotation may help you to ensure you catch required dependencies in your Spring wiring.

Maybe look into Maven which will give you explicit phases to bind your unit and integration tests on to. Maven is quite widely used in the Spring community.