quarkus: QuarkusTest**Callback not executed when running QuarkusIntegrationTest
Describe the bug
When running a @QuarkusIntegrationTest the registered QuarkusTest**Callback are not executed.
Setup:
integrationTest
|-src
| |-MyIntegrationTest.java (extends MyQuarkusTest)
|-resources
|-META_INF
|-services
|- io.quarkus.test.junit.callback.QuarkusTestBeforeEachCallback (same as in test)
test
|-src
| |-MyQuarkusTest.java
|-resources
|-META_INF
|-services
|- io.quarkus.test.junit.callback.QuarkusTestBeforeEachCallback
Expected behavior
The test callback should also be executed when running integration tests.
Actual behavior
When running a @QuarkusIntegrationTest the registered QuarkusTest**Callback are not executed.
How to Reproduce?
No response
Output of uname -a or ver
No response
Output of java -version
No response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.13.0.Final
Build tool (ie. output of mvnw --version or gradlew --version)
No response
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 15 (14 by maintainers)
Commits related to this issue
- Execute QuarkusTest**Callback when running QuarkusIntegrationTest Fix https://github.com/quarkusio/quarkus/issues/28402 Note that I had to add two "expensive" tests to verify that this works fine fo... — committed to Sgitario/quarkus by Sgitario 2 years ago
- Execute QuarkusTest**Callback when running QuarkusIntegrationTest Fix https://github.com/quarkusio/quarkus/issues/28402 Note that I had to add two "expensive" tests to verify that this works fine fo... — committed to Sgitario/quarkus by Sgitario 2 years ago
- Execute QuarkusTest**Callback when running QuarkusIntegrationTest Fix https://github.com/quarkusio/quarkus/issues/28402 Note that I had to add two "expensive" tests to verify that this works fine fo... — committed to Sgitario/quarkus by Sgitario 2 years ago
- Execute QuarkusTest**Callback when running QuarkusIntegrationTest Fix https://github.com/quarkusio/quarkus/issues/28402 Note that I had to add two "expensive" tests to verify that this works fine fo... — committed to Sgitario/quarkus by Sgitario 2 years ago
- Execute QuarkusTest**Callback when running QuarkusIntegrationTest Fix https://github.com/quarkusio/quarkus/issues/28402 Note that I had to add two "expensive" tests to verify that this works fine fo... — committed to igorregis/quarkus by Sgitario 2 years ago
- Execute QuarkusTest**Callback when running QuarkusIntegrationTest Fix https://github.com/quarkusio/quarkus/issues/28402 Note that I had to add two "expensive" tests to verify that this works fine fo... — committed to igorregis/quarkus by Sgitario 2 years ago
- Execute QuarkusTest**Callback when running QuarkusIntegrationTest Fix https://github.com/quarkusio/quarkus/issues/28402 Note that I had to add two "expensive" tests to verify that this works fine fo... — committed to igorregis/quarkus by Sgitario 2 years ago
- Execute QuarkusTest**Callback when running QuarkusIntegrationTest Fix https://github.com/quarkusio/quarkus/issues/28402 Note that I had to add two "expensive" tests to verify that this works fine fo... — committed to igorregis/quarkus by Sgitario 2 years ago
- Execute QuarkusTest**Callback when running QuarkusIntegrationTest Fix https://github.com/quarkusio/quarkus/issues/28402 Note that I had to add two "expensive" tests to verify that this works fine fo... — committed to tmihalac/quarkus by Sgitario 2 years ago
Would you like to look into this @Sgitario ?
It sounds a good idea to me as well, and it’s safer way to introduce this. But I would add this new property as part of the existing
TestConfig, something likequarkus.test.enable-callbacks-for-integration-tests.