It's not supported, but I'm sure it can be added. Also selection mode (as proposed in ScalaTest 2.0) also can be added. You can add issue to bugtracker. We just started again to improve ScalaTest and Specs2 support, so your issue can be fixed quite soon.
On 5/2/2012 3:58 PM, Alexander Podkhalyuzin wrote:
We just started again to improve ScalaTest and Specs2 support.
Hi Alexander,
Since you are improving testing support....Can you provide a way to execute unit tests separately from integration tests across a multi-module project? sbt uses the "it" directory for integration tests but the "test" directory for unit tests. It would be very helpful to execute unit tests quickly and separately from the long-running and externally dependent integration tests.
So "test" and "it" directories are placed in same module? And package structure is also the same? There are possibility to run tests only in single module or across module dependencies. But if both my questions has answer "yes" then this case is not covered by these possibilities. If it's wide practice to do so, it can be implemented, but I think it's better to use something different than just naming convention for directories.
It's not supported, but I'm sure it can be added. Also selection mode (as proposed in ScalaTest 2.0) also can be added.
You can add issue to bugtracker. We just started again to improve ScalaTest and Specs2 support, so your issue can be fixed quite soon.
Best regards,
Alexander Podkhalyuzin.
On 5/2/2012 3:58 PM, Alexander Podkhalyuzin wrote:
Hi Alexander,
Since you are improving testing support....Can you provide a way to
execute unit tests separately from integration tests across a
multi-module project? sbt uses the "it" directory for integration tests
but the "test" directory for unit tests. It would be very helpful to
execute unit tests quickly and separately from the long-running and
externally dependent integration tests.
Thanks,
Jon
You can already but you need to tag each test.
So "test" and "it" directories are placed in same module? And package structure is also the same?
There are possibility to run tests only in single module or across module dependencies.
But if both my questions has answer "yes" then this case is not covered by these possibilities. If it's wide practice to do so, it can be implemented, but I think it's better to use something different than just naming convention for directories.
Best regards,
Alexander Podkhalyuzin.