Some of our JUnit test cases, mainly DAO tests, have extended a base class BaseTransactionalIntegrationTest, which in turn extends deprecated Spring classes.This base class provided unit tests with a default Spring context and an automatic rollback capability. Unit tests extending this base class were automatically database-aware, and any updates done in the unit test were automatically rolled back at the end of the test.
Spring has deprecated the class that BaseTransactionalIntegrationTest extends, and now recommends a different way of coding integration unit tests (see Spring Javadoc). We have created a new abstract class that does not extend a Spring class, but uses Spring annotations to provide the same functionality.
All integration tests (i.e. JUnit tests that talk to the Oracle database and require a full Spring context) should now extend the new AbstractIntegrationTestBase class, found in the csf-test module.
In addition, to get the automatic rollback functionality, each JUnit test method should be annotated with @Transactional.