anchor.diff:  
   [NOTE]
   ====
  -You can enable persistence for the embedded mode by providing a path to a database file 
  +You can enable persistence for the embedded mode by providing a path to a database file
   in your configuration, e.g. `spring.data.neo4j.uri=file://var/tmp/graph.db`.
   ====
   
  
positive.code: ==== Using the Embedded Mode
  If you add `org.neo4j:neo4j-ogm-embedded-driver` to the dependencies of your application,
  Spring Boot automatically configures an in-process embedded instance of Neo4j that does
  not persist any data when your application shuts down. 
  
  [NOTE]
  ====
  As the embedded Neo4j OGM  driver  does not provide the Neo4j kernel itself, you have 
  to declare `org.neo4j:neo4j` as dependency yourself. Refer to 
  https://neo4j.com/docs/ogm-manual/current/reference/#reference:getting-started[the
  Neo4j OGM documentation] for a list of compatible versions.
  ====
  
  The embedded driver takes precedence over the other drivers when there are multiple
  drivers on the classpath. You can explicitly disable the embedded mode by setting 
  `spring.data.neo4j.embedded.enabled=false`. 
  
  <<boot-features-testing-spring-boot-applications-testing-autoconfigured-neo4j-test,Data Neo4j Tests>>
  automatically make use of an embedded Neo4j instance if the embedded driver and Neo4j
  
negative.code: a context for tests sharing the same configuration, the use of `@MockBean` or `@SpyBean`
  influences the cache key, which will most likely increase the number of contexts.
  
  PTIP: If you are using `@SpyBean` to spy on a bean with `@Cacheable` methods that refer
  to parameters by name, your application must be compiled with `-parameters`. This
  ensures that the parameter names are available to the caching infrastructure once the
  bean has been spied upon.
  