You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that the IntegrationTest config in sbt is deprecated we need a different way to run integration tests, preferably allowing to run them separately from unit tests.
The sbt recommendation is to create separate submodules for integration tests only, which works fine for regular Scala project but seems cumbersome for Kalix projects that would now need to become multi-module.
On the other hand if we come up with our own scheme, we'll have to be careful to choose something that IDEs will understand. Maybe we could rely on Scalatest tags? (https://www.scalatest.org/user_guide/tagging_your_tests)
The text was updated successfully, but these errors were encountered:
testOnly *Integration* works for running only the integration tests, and turns out we already have a separate sbt setting called onlyUnitTest for running only the unit tests (
Now that the
IntegrationTest
config in sbt is deprecated we need a different way to run integration tests, preferably allowing to run them separately from unit tests.The sbt recommendation is to create separate submodules for integration tests only, which works fine for regular Scala project but seems cumbersome for Kalix projects that would now need to become multi-module.
On the other hand if we come up with our own scheme, we'll have to be careful to choose something that IDEs will understand. Maybe we could rely on Scalatest tags? (https://www.scalatest.org/user_guide/tagging_your_tests)
The text was updated successfully, but these errors were encountered: