On 13 mars 2012, at 20:19, Sanne Grinovero wrote: My feeling is that most tests should be in core as the "TCK" to make sure each dialect is safe or see when it fails. So I would favor to move tests into core as much as possible. In your example, there is nothing MongoDB specific about @Embedded and we should make sure we indeed support that for all dialects. The tests that could stay in your won modules are tests that ensure that the embedded object is properly put in the document and not else where. That does not make much sense right now but I imagine that for collection of embeddable and when we support metadata driven datastore specific tuning, we will want to test such things. (ie collections of embeddable are in the document in mongo and outside in a different key in say Infinispan. Let's open a wiki page to document these discoveries that will help wannabe datastore contributors. Title: "How to write a Datastore in Hibernate OGM" in the hibernate ogm subspace. BTW, in eclipse and in intellij, you can say that you run a given (set of) test based on the classpath of a specific module. That will let you run the test with the mongodb settings stored in your hibernate.properties file.