You can start from the example in OGM-1263 Reopened , create a new one or get the inspiration from the existing tests for Wildfly (The one Guillaume Smet mentioned in the previous comment.

The goal of this test is not necessary to solve OGM-1263 Reopened , they are two separate issues. This is supposed to prove that we can use Spring with Hibernate OGM. Once we have something that works, we can start to check if we can reproduce the problem related to OGM-1263 Reopened . This is the first step to solve future problem related to the integration between Spring and OGM.

You can start from a dialect you are more familiar with but we want to be able to extend the example to the other dialects as well. The approach we use to test deployment on Widlfly seems the way to go: we have a single test and then we deploy it using different configurations to test the different dialects. Everything related to a dialect is stored in the package related to the dialect we want to test.

This is a relative open issue, you can propose a solution, what we are interested is to see that we can start an application and execute some CRUD operations using Spring + Hibernate OGM. You can create something relative simple and then we build on top of it.

I think you should start by moving the current integrationtest under a new submodule like Guillaume Smet suggested. I think you need to understand how our integration tests with WildFly works anyway, before working on this issue.