如何隔离集成测试？

Question

When having a database operations in many integration Tests, how to be sure that the state of the DataBase is the same before and after any Test in an automatic manner (with some framework) ?

I am not interested in the manual manner ( @Before @After )

Answer 1

What we do at my company is that

1. We use transactions to ensure that the DB is in the same state after the test as beforehand.
2. We use test scripts that ensure valid test data (eg, inserting some additional rows to some tables for specific test scenarios, whereas updating some others). You can execute these scriptes in setUp methods to reuse them by multiple test cases or even define them in utility classes that can be reused by multple test suites.

This works finy in many scenarios, however, it may be problematic if you try to test parts of your application that are working with nested transactions.