Skip to content
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

Integration tests are broken (because using @Inject) #119

Open
clementguillot opened this issue Apr 22, 2024 · 0 comments
Open

Integration tests are broken (because using @Inject) #119

clementguillot opened this issue Apr 22, 2024 · 0 comments

Comments

@clementguillot
Copy link
Owner

Description

Almost all our integration tests are broken. Just run ./gradlew :apps:server:testNative to observe.

This is due to usage of @Inject properties in test classes, as documented here:

It is also possible to test native executables using @QuarkusIntegrationTest. This supports all the features mentioned in this guide except injecting into tests (and the native executable runs in a separate non-JVM process this is not really possible).

So, we need to refactor our tests, to no longer rely on injected fields, and use HTTP endpoints or CLI commands instead.

@clementguillot clementguillot converted this from a draft issue Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

1 participant