Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-19211

Fix TestDefaultPageProviders.checkCoreQueryAndFetch on MongoDB

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.10-HF07, 8.2
    • Component/s: Core MongoDB, Tests
    • Tags:
    • Story Points:
      0

      Description

      These two tests fail on MongoDB:

      • TestDefaultPageProviders.checkCoreQueryAndFetch
      • TestDefaultPageProviders.checkCoreQueryAndFetchReference
      java.lang.AssertionError: expected:<1> but was:<4>
      	at org.junit.Assert.fail(Assert.java:88)
      	at org.junit.Assert.failNotEquals(Assert.java:743)
      	at org.junit.Assert.assertEquals(Assert.java:118)
      	at org.junit.Assert.assertEquals(Assert.java:555)
      	at org.junit.Assert.assertEquals(Assert.java:542)
      	at org.nuxeo.ecm.platform.contentview.jsf.test.TestDefaultPageProviders.checkCoreQueryAndFetch(TestDefaultPageProviders.java:529)
      	at org.nuxeo.ecm.platform.contentview.jsf.test.TestDefaultPageProviders.testCoreQueryAndFetch(TestDefaultPageProviders.java:499)
      

      The test is asserting the exact number keys in a map returned by queryAndFetch but MongoDB actually returns extra keys like ecm:uuid, ecm:parentId and ecm:name.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                PagerDuty

                Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.