-
Notifications
You must be signed in to change notification settings - Fork 174
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
MockHeroProxy doesn't work with 2.14 #199
Comments
Shouldn't you use @InjectMock ? |
Shouldn't you use imperative code and use Loom ? ;o) |
I mean, the stack trace indicates that it's not a mock. So the mock is not configured. When using the rest client, I only use @InjectMock, and not @mock. |
Unfortunately it will have to wait my weekend nightshift. |
@agoncal how can I reproduce that issue from this repo? |
Also, I don't know what we should recommend now: |
How do I reproduce the problem? The stack trace is not very useful.
I think that this could be another problem related to quarkusio/quarkus#28429. @manovotn Could it be fixed with quarkusio/quarkus#29155?
It depends. AFAIK |
|
Yes, this could be it. I recall the fix was also related to mocking.
Yeah, that's a way to go! |
@agoncal @mkouba @cescoffier this issue is gone when I use |
+1 |
@geoand feel free to close it, seems I lack the permissions on this repo... |
I'll let @cescoffier have the final say :) |
Fixed with #208 |
@cescoffier now that the
HeroResource
uses reactive mode, mocking doesn't seem to work. In our documentation we use the same mocking mecanism for imperative and reactive:But when executing the tests, we get the following error:
The text was updated successfully, but these errors were encountered: