@DatabaseTearDown("/resetDB.xml")
public class CSVConfigTests {
@Test
@ExpectedDatabase(assertionMode = DatabaseAssertionMode.NON_STRICT, value = "dataVerificationTest.xml")
public void shouldImportCSV() throws Exception {
// db imports
}
}
when shouldImportCSV fails due to @ExpectedDatabase assertion, @DatabaseTearDown doesn't work as data still remains in database. Is this by design or a bug?
Failure of tearDown causes other tests to fail as well.
I have the following setup:
when shouldImportCSV fails due to @ExpectedDatabase assertion, @DatabaseTearDown doesn't work as data still remains in database. Is this by design or a bug?
Failure of tearDown causes other tests to fail as well.