-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Add tests for redis dev services behaviour in devmode #47968
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
Add tests for redis dev services behaviour in devmode #47968
Conversation
f8fd700
to
9f95e9f
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
d7fd46e
to
20866b2
Compare
This comment has been minimized.
This comment has been minimized.
20866b2
to
6ddda62
Compare
This comment has been minimized.
This comment has been minimized.
"Expected random port 6377, but got: " + Arrays.toString(container.getPorts())); | ||
|
||
test.modifyResourceFile("application.properties", | ||
s -> ContinuousTestingTestUtils.appProperties("quarkus.redis.devservices.port=6377")); |
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.
Suggest using the FIXED_PORT_PROPERTIES
constant here.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Status for workflow
|
While working on #47610, I realised we didn't have much coverage of continuous testing and the redis dev services.
I've added tests to make sure that dev services work, and that containers are (a) updated or (b) reused when the app changes. I expected that disabling dev services would make the dev service go away, but that's not currently working, so I've disabled that test.