Issues running tests under Moqui 4.0

Technical Questions
1

When creating a new top level app repo:

      framework/   # cloned moqui-framework repo

I am running into an issue with test failures.

The first time I run ./gradlew clean build load test from framework I get one test failed

image
image820×542 33.7 KB

when I run ./gradlew clean build test I end up with: Multiple failures

  • EntityFindTests. [auto cache clear for view list on create of record not included](../classes/EntityFindTests.html#auto cache clear for view list on create of record not included)
  • EntityNoSqlCrud. [createBulk TestNoSqlEntity](../classes/EntityNoSqlCrud.html#createBulk TestNoSqlEntity)
  • ToolsScreenRenderTests. [render DataView screens](../classes/ToolsScreenRenderTests.html#render DataView screens)
  • ToolsScreenRenderTests. [render tools screen AutoScreen/AutoFind/create?aen=moqui.test.TestEntity&testId=TEST_SCR&testMedium=Screen Test Example (, )](../classes/ToolsScreenRenderTests.html#render tools screen AutoScreen/AutoFind/create?aen=moqui.test.TestEntity&testId=TEST_SCR&testMedium=Screen Test Example (, ))
  • ToolsScreenRenderTests. [render tools screen Service/ServiceRun/run?serviceName=org.moqui.impl.UserServices.create#UserAccount&username=ScreenTest&newPassword=moqui1!!&newPasswordVerify=moqui1!!&userFullName=Screen Test User&emailAddress=screen@test.com (, )](../classes/ToolsScreenRenderTests.html#render tools screen Service/ServiceRun/run?serviceName=org.moqui.impl.UserServices.create#UserAccount&username=ScreenTest&newPassword=moqui1!!&newPasswordVerify=moqui1!!&userFullName=Screen Test User&emailAddress=screen@test.com (, ))

When I went looking I can find any built in CI/CD framework configuration that indicates that these tests are exercised for every check in so I don’t know if I should expect these tests to work or not.

Question 1: Should I expect that the tests will run out of the box ?
Question 2: Is there any CI/CD structure that exercises these tests routinely?

2

The tests run when using common demo repos. If you are using something like moqui-hazelcast or other custom components then it might cause issues. The failures you’re seeing are mostly race conditions or timing issues (query before the thing is available in cache in elasticesarch). Hazelcast specifically can trigger this.