-
Notifications
You must be signed in to change notification settings - Fork 36
Allow running arbitrary sbt tasks/commands with docker-compose #44
Comments
I've just cloned this project with the intent of having a go at this one. I too fancy using this with cucumber, so worth having a shot |
Partial fix for issue #44 — added cucumber support
Thanks! 👍 |
@kurtkopchik: I have a similar use case with the gatling sbt plugin (I want to run some simple functional tests using gatling as well as regular ScalaTests). Any advice how to go about it? |
Hi @eugenemiretsky - I would start by looking at pull request (0fdfa13) that added support for Cucumber (0fdfa13#diff-d97efb1099d050d6a60fbf8c9cf6447eR96) and see how you can add support in a similar fashion for Gatling via |
It would be really nice if there was a way to run an arbitrary task when docker compose is up. For example, if I wanted to run a code coverage on the tests executed by dockerComposeTest, is there a way to do it? |
Please support running arbitrary sbt tasks/commands while the docker-compose containers are up, not just ScalaTest.
I'm attempting to write my integration/acceptance-tests using cucumber-scala instead of ScalaTest. Currently I'm forced to do this via a ScalaTest wrapper-test-case which "manually" invokes cucumber.runtime.Runtime.run() and fail the test in case Runtime.exitstatus != 0, since the sbt cucumber plugin cannot be invoked from sbt-docker-compose it appears.
I understand that you'd then miss out on the possibility to use the ScalaTest specific ConfigMap, however environment variables (system properties) still work fine in those cases.
However, the application I'd like to test better uses Akka Cluster Sharding, so I think it would be more straightforward to use Akka's multi-jvm or maybe even multi-node support which are implemented as sbt plugins plus test libraries. Would be awesome if sbt-docker-compose could support that as well. Those are however based on ScalaTest, so think I might better give in and switch from cucumber to ScalaTest's FeatureSpec instead.
If you want to look into it, a similar sample project with multi-jvm tests (but no sbt-docker-compose usage yet) is available at https://github.com/typesafehub/activator-akka-cluster-sharding-scala
The text was updated successfully, but these errors were encountered: