-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gardening: remove use of IntegrationTest scope #1666
Conversation
92f582d
to
f32ec27
Compare
The integration tests ran and worked, but I don't see why "Build and Test" didn't execute properly. |
Rebased on main |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good but have opinions on test code in src/main vs making the dependency test scoped.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see that I reviewed this a long while ago but never submitted my comments. Here they are. Not sure if they are outdated by now?
.settings( | ||
name := "akka-stream-kafka-tests", | ||
libraryDependencies ++= Seq( | ||
"com.typesafe.akka" %% "akka-discovery" % akkaVersion, | ||
"com.google.protobuf" % "protobuf-java" % "3.23.3", // use the same, or later, version as in scalapb | ||
"org.testcontainers" % "kafka" % testcontainersVersion, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would have expected that this project would not need test containers, but that would be in integrationTests
? Benchmarks could depend on integrationTests if that is the reason.
One advantage of that is that it's more clear when someone adds such tests that it should be in the integrationTests project and not in tests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Most Alpakka Kafka tests need a Kafka instance to talk to, they share a Kafka provided via TestContainers.
The difference for the Integration Tests is that they run test specific Kafkas TestcontainersKafkaPerClassLike
with specific configuration.
Very few classes from 'tests' are referenced from the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
One thought after starting on something parallel in akka-management, can we follow a common naming scheme for these, I think the recommendation in the sbt deprecation was |
Build success! |
7f10dd3
to
45dd000
Compare
Rebased in the hope that the updated GH actions from |
System.IO.IOException: No space left on device : '/home/runner/runners/2.314.1/_diag/Worker_20240308-111255-utc.log' |
Something to try: actions/runner-images#2840 (comment) |
The
IntegrationTest
scope is deprecated since sbt 1.9.Moving integration tests to a separate project instead which now depends on the
tests
project for shared code and dependencies.Refs