I really like Spring, so I tend to use its features to the fullest. However, in some dark corners of its philosophy, I tend to disagree with some of its assumptions. One such assumption is the way database testing should work. In this article, I will explain how to configure your projects to make Spring Test and DBUnit play nice together in a multi-developers environment.
Introduction to DBUnit With the developed use of JUnit, many additions were made to it. These additions take advantage of the pluggable nature of JUnit. One of these contribution is DBUnit. DBUnit enables your unit tests to: preload the database with datas pertaining to your current test only,run your unit test (as usual),remove the data you preloaded in order to put the database in the same it was before your additions. In effect, you can now test your DAO classes. Let’s take a (very)