-
Notifications
You must be signed in to change notification settings - Fork 8.1k
Add tests that run with distribution placed in a directory with special characters #46301
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
base: main
Are you sure you want to change the base?
Add tests that run with distribution placed in a directory with special characters #46301
Conversation
|
Looking at the |
mabartos
left a comment
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.
@michalvavrik LGTM, thanks!
@shawkins You want to review if it covers all scenarios as for the fix?
@michalvavrik The CI failures are unrelated, and the fix for them is already in the main branch, so you can just rebase.
quarkus/tests/integration/src/test/java/org/keycloak/it/cli/dist/AbstractPathDistTest.java
Outdated
Show resolved
Hide resolved
Adds tests for keycloak#45971 (fixed by keycloak#45972). Closes: keycloak#46135 Signed-off-by: Michal Vavřík <[email protected]>
90b24c7 to
26b0e27
Compare
vmuzikar
left a comment
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.
@michalvavrik Looks good, thank you. Alternative approach would've been running Quarkus tests in the CI from a different subdir with special characters but this works too.
| @BeforeStartDistribution(AddCustomScriptsProvider.class) | ||
| @RawDistOnly(reason = "Testing installation path handling") | ||
| @Test | ||
| @Launch(Build.NAME) |
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.
Just a nitpick. I think just testing start or start-dev would be enough as build is done implicitly. But we can keep as is.
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.
@vmuzikar Yep, nice point.
Adds tests for #45971. I have run tests added in this PR after reverting the fix #45972 and they verify the issue.