Akka multi-jvm test must explicitly run

Question

When using the sbt "multi-jvm: test" command, there are no tests to run in sbt reports. However, if I explicitly run the test, for example. "multi-jvm: run package.testName", then they work fine.

I use the default convention {TestName} MultiJvm {NodeName}, and the default path for src / multi-jvm / scala

Edit:

This is what happens when I run only test

multi-jvm:test-only multijvm.commands.CommandsAreSentToRegisteredHandlers_ [info] Compiling 1 Scala source to /mnt/repos/akkesb/target/classes... [info] No tests to run. 

But here is how I can make it work

 > multi-jvm:run multijvm.commands.CommandsAreSentToRegisteredHandlers_ [info] * multijvm.commands.CommandsAreSentToRegisteredHandlers_ [JVM-_MarketingServiceHost] [ERROR] [06/10/2013 20:22:30.608] [akkesb-akka.actor 

Here is my marker:

 > multi-jvm:multi-jvm-marker [info] MultiJvm 

Specific Tests:

 > multi-jvm:multi-jvm-marker [info] MultiJvm 

Answer 1

1) please check multiJvmMarker in MultiJvm

I have multiJvmMarker in MultiJvm := "_j"

So tests without suffix _j not executed

2) please check definedTests in MultiJvm

I have, for example, definedTests in MultiJvm <<= definedTests in Test

You should see something like

 > show multi-jvm:defined-tests [info] List(Test org.digimead.digi.lib.rudp.RUDPTest_j1 : subclass(false, org.scalatest.Suite), Test org.digimead.digi.lib.rudp.RUDPTest_j2 : subclass(false, org.scalatest.Suite) 

Did your test start with test-only ? In fact, I can start with

multi-jvm:test-only org.digimead.digi.lib.rudp.RUDPTest

Note the suffix _j . In your case, this may be different.

Updated:

An example is a simple client / server test that uses MultiJVM: RUDPTest