-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Added tests for KubernetesClient serialization/deserialization #41274
Added tests for KubernetesClient serialization/deserialization #41274
Conversation
Should ensure that (de)serialization works as expected both in JVM and Native modes. Signed-off-by: Marc Nuri <[email protected]>
Status for workflow
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
...-client/src/test/java/io/quarkus/it/kubernetes/client/KubernetesClientSerializationTest.java
Show resolved
Hide resolved
.build()) | ||
.create(); | ||
// JSON data is retrieved from the mock server | ||
when() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this really verifying that the JSON shape is the expected one and not the one with all the empty objects/arrays? #39934 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AFAIK, it should.
In any case, if you want to verify manually you can change line 113 from
.log().ifValidationFails(LogDetail.BODY);
to
.log().body();
We can also add another assertion to verify that the response body doesn't actually contain the word overhead
:
.body(not(containsString("overhead"))
Should ensure that (de)serialization works as expected both in JVM and Native modes.
Relates to #39934
/cc @galderz