-
Notifications
You must be signed in to change notification settings - Fork 196
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
jt400 mock coverage + native fixes #5812
Conversation
b75ddc8
to
d29bf5b
Compare
...ion-tests/jt400/src/test/java/org/apache/camel/quarkus/component/jt400/it/Jt400MockTest.java
Outdated
Show resolved
Hide resolved
...oyment/src/main/java/org/apache/camel/quarkus/component/jt400/deployment/Jt400Processor.java
Outdated
Show resolved
Hide resolved
d29bf5b
to
de8871f
Compare
@jamesnetherton All changes are amended into the PR. |
@JiriOndrusek need backport to |
@JiriOndrusek I still see the |
de8871f
to
eaf906b
Compare
Sorry for that, I fixed 1 place and there were others. I checked the PR now and there is no such occurrence anymore/ |
Thanks for the reminder! I added the label. |
fixes #5809
The mocked tests require
quarkus.test.flat-class-path
to betrue
. (default behavior for the tests)New profile
skip-mock-tests
returns flat-class-path tofalse
and disables all mocked tests.Profile is not active by default and can be activated by property
-Dskip-mock-tests=true
for the execution.Test coverage is quite small - there are tests to read/write for keyed data-queue and message-queue, and the test for the program call.
Mocked backend is not based on the real server, therefore the response are probably far from the real responses
This mocked tests could be refactored in the future to mimic real responses. Now it allows extension to be tested in the native mode (to some extent).