Comments on: Three reasons why you don’t want to use a Spring context in unit tests http://maxheapsize.com/2009/02/25/three-reasons-why-you-dont-want-to-use-a-spring-context-in-unit-tests/ Oliver Wehrens on Programming and Agile Sun, 24 Jul 2011 10:50:52 +0000 hourly 1 http://wordpress.org/?v=3.1.2 By: Oliver Wehrens http://maxheapsize.com/2009/02/25/three-reasons-why-you-dont-want-to-use-a-spring-context-in-unit-tests/comment-page-1/#comment-4272 Oliver Wehrens Thu, 04 Feb 2010 23:00:37 +0000 http://maxheapsize.com/?p=90#comment-4272 For integration tests, absolutely. You need some tests in the end which ensure everything is working together. But this should be just a handful of tests covering the most critical paths of your applications. For integration tests, absolutely.

You need some tests in the end which ensure everything is working together. But this should be just a handful of tests covering the most critical paths of your applications.

]]> By: Otavio Macedo http://maxheapsize.com/2009/02/25/three-reasons-why-you-dont-want-to-use-a-spring-context-in-unit-tests/comment-page-1/#comment-4265 Otavio Macedo Thu, 04 Feb 2010 13:40:21 +0000 http://maxheapsize.com/?p=90#comment-4265 I agree with you. Unit tests should be as simple as possible. On the other hand, using Spring in integration tests is a good idea. Especially those tests that interact with databases. Spring has some base classes for test cases that handle transactions, bean caching etc. I agree with you. Unit tests should be as simple as possible. On the other hand, using Spring in integration tests is a good idea. Especially those tests that interact with databases. Spring has some base classes for test cases that handle transactions, bean caching etc.

]]>