I have several tests which extend AbstractTransactionalDataSourceSpringContextTests and they appear to not be rolling back as expected when I run more than one of them together, as in the case of my
Maven build. I get tests failing because they expect the database tables to be in a clean state when they start, and instead there is data already present, making it impossible to assert that a certain number of records are present after using DAO classes to save/delete/etc.
I have confirmed that this behavior happens using both HSQLDB and Derby embedded databases.
Can anyone suggest something I can try to find the source of this problem?
Thanks in advance for any assistance.
--James
[ December 17, 2008: Message edited by: James Adams ]