Multiple QuarkusTestResource annotations in Test are ignored
See original GitHub issueDescribe the bug
Multiple @QuarkusTestResource
annotations in Test are completely ignored
e.g.
@QuarkusTest
@QuarkusTestResource(ActiveMQServerTestResource.class)
@QuarkusTestResource(ActiveMQClientTestResource.class)
Expected behavior
Given that QuarkusTestResource
annotation is Repeatable
both test resources should be processed.
Actual behavior Both QuarkusTestResource are ignored
To Reproduce Steps to reproduce the behavior:
- Create a test with two simple “QuarkusTestResource” test resources
- Run test
- See that both QuarkusTestResource are ignored. If you comment one of them just 1 is picked and processed correctly.
Issue Analytics
- State:
- Created 4 years ago
- Comments:15 (11 by maintainers)
Top Results From Across the Web
Testing Your Application - Quarkus
QuarkusTestResource } class * annotation will be used for the tests using this ... will be started, * global annotated test resources will...
Read more >java - Different @QuarkusTestResource per Quarkus profile
I have just set up my project to use H2DatabaseTestResource in the tests. I also have created a custom ...
Read more >Testing Quarkus Applications | Baeldung
This test, annotated with @QuarkusTest, first starts the Quarkus application and then performs a series of HTTP requests against our ...
Read more >Testing Quarkus Web Applications: Writing Clean Component ...
TestSecurity annotation to control the security context the test is run with. ... If multiple Quarkus Test Resources are defined, @QuarkusTestResource has ...
Read more >How to Test Quarkus applications - Mastertheboss
The most important part of the Quarkus testing framework is the annotation io.quarkus.test.junit.QuarkusTest. When you annotate a test class ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@lkrzyzanek Yes, that’s expected - for repeatable annotations you get the “container” annotation.
@gastaldi Thanks for the reproducer!
Nicely works in 1.0.0.CR2. Thanks guys!