camunda.cfg.prefix.xml configuration is not taken into account because of DbSchemaPrefixTestHelper

XMLWordPrintable

    • Type: Task
    • Resolution: Fixed
    • Priority: L3 - Default
    • 7.13.0, 7.13.0-alpha1
    • Affects Version/s: None
    • Component/s: None
    • None

      There are failing webapp unit tests:

      • org.camunda.bpm.cockpit.plugin.base.IncidentRestServiceTest.testQueryByProcessInstanceIdAndActivityId (webapp)
      • org.camunda.bpm.cockpit.plugin.history.tenantcheck.HistoricProcessInstanceRestServiceTenantCheckTest.queryHistoricProcessInstanceCountWithAuthenticatedTenant (platform-ee)

       

      [ERROR] testQueryByProcessInstanceIdAndActivityId(org.camunda.bpm.cockpit.plugin.history.HistoricIncidentRestServiceTest)  Time elapsed: 0.772 s  <<< FAILURE!
java.lang.AssertionError:
Database is not clean:
Table: SCHEMA1.ACT_RU_METER_LOG contains: 10 rows        at org.junit.Assert.fail(Assert.java:88)
        at org.camunda.bpm.engine.impl.test.TestHelper.assertAndEnsureCleanDbAndCache(TestHelper.java:347)
        at org.camunda.bpm.engine.impl.test.TestHelper.assertAndEnsureCleanDbAndCache(TestHelper.java:303)
        at org.camunda.bpm.engine.test.ProcessEngineRule.finished(ProcessEngineRule.java:232)
        at org.junit.rules.TestWatcher.finishedQuietly(TestWatcher.java:117)
        at org.junit.rules.TestWatcher.access$400(TestWatcher.java:46)
        at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:64)
        at org.camunda.bpm.engine.test.ProcessEngineRule$1.evaluate(ProcessEngineRule.java:172)
        at org.junit.rules.RunRules.evaluate(RunRules.java:20)
        at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
        at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
        at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
        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.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
        at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
        at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
        at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
        at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
        at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
        at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
        at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
        at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
        at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
        at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)

      Hint: The database is not cleaned up because the metrics cannot disabled via the camunda.cfg.prefix.xml as the database tables are created via org.camunda.bpm.webapp.impl.test.util.DbSchemaPrefixTestHelper

       

      AT:

      • disable the metrics reporter in the DbSchemaPrefixTestHelper and camunda.cfg.prefix.xml
      • add hint in camunda.cfg.prefix.xml to check DbSchemaPrefixTestHelper in such cases.

       

        This is the controller panel for Smart Panels app

              Assignee:
              Nikola Koevski
              Reporter:
              Yana Vasileva
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: