【问题标题】:Exception during teardown in a Transactional DbUnit testTransactional DbUnit 测试中的拆卸过程中的异常
【发布时间】:2018-10-24 11:39:09
【问题描述】:

测试类声明

@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration(classes = { TestH2Config.class })
@TestExecutionListeners({
        DependencyInjectionTestExecutionListener.class,
        DbUnitTestExecutionListener.class,
        TransactionalTestExecutionListener.class
})
@TransactionConfiguration(defaultRollback = true)
@Transactional
public class BookServiceIT {
    // ... dependencies injection goes here (omitted for brevity)
    @Test
    @DatabaseSetup("/datasets/import.xml")
    public void testCase1() throws Exception {
        // .. create Book in Organization(id=2)
        // ... read and create data in database (omitted for brevity)
    }
}

测试/资源/数据集/import.xml

<?xml version='1.0' encoding='UTF-8'?>
<dataset>
  <Organization id="2" name="Gov. Library" inactive="false" />
</dataset>

用于运行测试的 Maven 命令:

mvn verify -T 1C

我正在附加异常堆栈跟踪(仅在 Codeship Linux 环境中测试失败):

WARNING: Caught exception while allowing TestExecutionListener [com.github.springtestdbunit.TransactionDbUnitTestExecutionListener@3f191a96] to process 'before' execution of test method [public void com.test.integration.BookServiceIT.testCase1() throws java.lang.Exception] for test instance [com.test.integration.BookServiceIT@15f18e5] org.h2.jdbc.JdbcSQLException: Referential integrity constraint violation: "FK_JNCMPQJWFCJEXX62EA1P06VLP: ITEST.BOOK FOREIGN KEY(LIBRARY_ID) REFERENCES ITEST.ORGANIZATION(ID) (2)"; SQL statement:delete from ORGANIZATION [23503-195]
        at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
        at org.h2.message.DbException.get(DbException.java:179)
        at org.h2.message.DbException.get(DbException.java:155)
        at org.h2.constraint.ConstraintReferential.checkRow(ConstraintReferential.java:425)
        at org.h2.constraint.ConstraintReferential.checkRowRefTable(ConstraintReferential.java:442)
        at org.h2.constraint.ConstraintReferential.checkRow(ConstraintReferential.java:317)
        at org.h2.table.Table.fireConstraints(Table.java:976)
        at org.h2.table.Table.fireAfterRow(Table.java:994)
        at org.h2.command.dml.Delete.update(Delete.java:101)
        at org.h2.command.CommandContainer.update(CommandContainer.java:101)
        at org.h2.command.Command.executeUpdate(Command.java:260)
        at org.h2.jdbc.JdbcStatement.executeInternal(JdbcStatement.java:193)
        at org.h2.jdbc.JdbcStatement.execute(JdbcStatement.java:165)
        at org.apache.commons.dbcp.DelegatingStatement.execute(DelegatingStatement.java:264)
        at org.apache.commons.dbcp.DelegatingStatement.execute(DelegatingStatement.java:264)
        at org.dbunit.database.statement.SimpleStatement.executeBatch(SimpleStatement.java:69)
        at org.dbunit.operation.DeleteAllOperation.execute(DeleteAllOperation.java:126)
        at org.dbunit.operation.CompositeOperation.execute(CompositeOperation.java:79)
        at com.github.springtestdbunit.DbUnitRunner.setupOrTeardown(DbUnitRunner.java:162)
        at com.github.springtestdbunit.DbUnitRunner.beforeTestMethod(DbUnitRunner.java:60)
        at com.github.springtestdbunit.DbUnitTestExecutionListener.beforeTestMethod(DbUnitTestExecutionListener.java:160)
        at com.github.springtestdbunit.TestExecutionListenerChain$3.call(TestExecutionListenerChain.java:93)
        at com.github.springtestdbunit.TestExecutionListenerChain.runChain(TestExecutionListenerChain.java:126)
        at com.github.springtestdbunit.TestExecutionListenerChain.forwards(TestExecutionListenerChain.java:115)
        at com.github.springtestdbunit.TestExecutionListenerChain.beforeTestMethod(TestExecutionListenerChain.java:91)
        at org.springframework.test.context.TestContextManager.beforeTestMethod(TestContextManager.java:249)
        at org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:74)
        at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:86)
        at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:70)
        at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
        at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:224)
        at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:83)
        at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
        at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
        at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
        at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
        at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
        at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
        at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)
        at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
        at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:163)
        at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
        at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
        at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
        at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
        at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
        at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
        at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)

我尝试使用其他执行侦听器(我在 DbUnit documentation 中找到),但我遇到了同样的异常...

@TestExecutionListeners({
        DependencyInjectionTestExecutionListener.class,
        DirtiesContextTestExecutionListener.class,
        TransactionDbUnitTestExecutionListener.class
})

UPD.:我尝试添加显式拆解:在 testCase() 方法的末尾删除了 Book。但异常仍然存在。

【问题讨论】:

  • 如果你使用@DatabaseTearDown注解会发生什么?您可能对隐式删除是正确的,但很可能 Spring 不太了解您的数据库约束。
  • @SeverityOne 我没有找到这个注解的任何好的使用例子。但是在查看时,我遇到了一个有用的属性@DatabaseSetup(正如您在下面的答案中看到的那样)。感谢您朝着正确的方向前进!

标签: java h2 spring-test dbunit teardown


【解决方案1】:

dbUnit 以与数据集文件中列出的数据相反的顺序删除行。确保文件的外键行位于具有主键/关系一侧的行之后。

更新: 测试中存在 book 表行,因此请告诉 dbUnit 也将其删除。一种方法是将外键表的空表添加到数据集文件主表之后:

<book/>

所以 dbUnit 拆卸操作会看到该表并清理它。

【讨论】:

  • 我的数据集 import.xml 与问题中显示的一样简单。图书实体未在数据集中列出;它是在测试期间创建的。
  • 要删除该行,请按照我在“更新”中所写的那样向数据集添加一个条目。
  • 请注意,正确的空标签语法是&lt;book&gt;&lt;/book&gt;&lt;book/&gt;,而不是&lt;/book&gt;
  • 在数据文件末尾添加关系表对我有用。有关更多信息,请参阅 DatabaseOperation.CLEAN_INSERT 在运行测试之前清理数据文件中提到的表
【解决方案2】:

它在你的堆栈跟踪中说:

org.h2.jdbc.JdbcSQLException: Referential integrity constraint violation: "FK_JNCMPQJWFCJEXX62EA1P06VLP: ITEST.BOOK FOREIGN KEY(LIBRARY_ID) REFERENCES ITEST.ORGANIZATION(ID) (2)"; SQL statement:delete from ORGANIZATION [23503-195]

因此,当BOOK 表中仍有通过FK_JNCMPQJWFCJEXX62EA1P06VLP 外键引用ORGANIZATION 表的记录时,您将从表ORGANIZATION 中删除。

你有特殊的代码来拆除数据库吗?如果没有,您可能需要明确地编写它,或者如果您的业务需求允许,将您的外键定义为 ON DELETE CASCADE

【讨论】:

  • 不,我没有专门的代码来拆除数据库。我相信这个删除是隐式发生的(由 Spring Transaction 或 DbUnit 管理)。
  • 请看更新:显式拆解(即删除图书)没有帮助。
【解决方案3】:

我通过指定type = DatabaseOperation.REFRESH 更改了 DbUnit 的行为。现在测试后没有清理数据库,也没有JDBC异常。

@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration(classes = { TestH2Config.class })
@TestExecutionListeners({
        DependencyInjectionTestExecutionListener.class,
        DirtiesContextTestExecutionListener.class,
        TransactionDbUnitTestExecutionListener.class
})
@Transactional
public class BookServiceIT {
    // ... dependencies injection goes here (omitted for brevity)
    @Test
    @DatabaseSetup(value = "/datasets/import.xml", type = DatabaseOperation.REFRESH)
    public void testCase1() throws Exception {
        // .. create Book in Organization(id=2)
        // ... read and create data in database (omitted for brevity)
        // .. delete the Book
    }
}

请参阅@DatabaseSetup 文档。

【讨论】:

  • 这种方法将测试结果留在数据库中,因此后续测试可能会出现错误的失败。
  • @Jeff,我同意这看起来不是一个好的解决方案。我只是把它贴在这里,因为它对我有用。
猜你喜欢
  • 1970-01-01
  • 1970-01-01
  • 2012-12-10
  • 2015-12-01
  • 1970-01-01
  • 1970-01-01
  • 2015-11-25
  • 1970-01-01
  • 1970-01-01
相关资源
最近更新 更多