1 - Testing Neo4j Methods
- Neo4j’s Test Harness
- Neo4j’s Embedded
- TestContainer’s Neo4j Module
2 - Comparisons
Using Harness and/or the Neo4j’s Embedded requires adding dependencies. This inevitably pollutes the test classpath leading to various issues, for example
- having conflicting versions of libraries on the classpath (the culprits are usually Lucene, Jetty or Scala), see for example this issue
- Spring auto-configuration is affected by presence of certain classes on classpath
- non-determinism - your code either sometimes fails, or fails only in certain environments