Replies: 1 comment
-
The only way I found to effectively test a the 2nd extension consumes the BuildItem from the real extension and produces a CDI bean, totally synthetic, containing the data (from the BuildItem) I want to test. Then, in the tests of the 2nd extension, make assertions on the resulting bean instances (hence containing the data from the BuildItem of the real extension): I haven't found a simpler way for this yet 🤷 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, per $subject I'm looking for a way to test (in
-deployment
module of) the extension BuildItem, produced by my extension.I haven't found a good way so far.
src/test/java
: a class with a method annotated@BuildStep
and taking the BuildItem as a parameter, so to do something about the builditem only during testing, but that is allegedly not picked up@Inject
the (Single)BuildItem into the test class having theQuarkusUnitTest
extension, but CDI unsatisfiedI just would like to make some assertions on the builditem, without introducing behaviour which would end up in the "set of behaviours" of the final end user (of the extension).
Any guidance, please?
Thanks 🙏
Beta Was this translation helpful? Give feedback.
All reactions