TestKit dependency on cassandra-persistance makes impossible to run tests inside IDEA

When running tests from IDEA using JDBC Persistence, they typically fail because the testkit tries to locate/connect to cassandra:

2018-02-26 15:31:00,482 INFO  com.datastax.driver.core.GuavaCompatibility - Detected Guava >= 19 in the classpath, using modern compatibility layer
2018-02-26 15:31:04,588 WARN  akka.persistence.cassandra.journal.CassandraJournal - Failed to connect to Cassandra and initialize. It will be retried on demand. Caused by: Timed out after 2 seconds while waiting for a ServiceLocator. Have you configured one?
2018-02-26 15:31:04,588 WARN  akka.persistence.cassandra.snapshot.CassandraSnapshotStore - Failed to connect to Cassandra and initialize. It will be retried on demand. Caused by: Timed out after 2 seconds while waiting for a ServiceLocator. Have you configured one?
2018-02-26 15:31:04,595 ERROR com.lightbend.lagom.internal.scaladsl.persistence.PersistentEntityActor - Persistence failure when replaying events for persistenceId [MyEntity|abcdefgh]. Last known sequence number [0]
com.lightbend.lagom.internal.persistence.cassandra.NoServiceLocatorException: Timed out after 2 seconds while waiting for a ServiceLocator. Have you configured one?

This is strange because if you are using JDBC Persistence you should not depend on Cassandra at all.

Lagom Version (1.2.x / 1.3.x / etc)

1.4.0

[TimMoore]

Reopening… @ignasi35 I think we should fix this. It isn’t working as you would expect. Note that @edmondo1984 is not using mixed persistence, but this issue arises because TestKit has a dependency on the Cassandra persistence library.

I think we need to fix this so that when you explicitly opt into JDBC using TestKit, it sets these properties for you automatically.

[TimMoore]

I’ve started working on a fix for this.