Skip to content
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

Compare json object values instead of byte streams when matching bodies that are content-type json #8860

Merged
merged 7 commits into from
Aug 25, 2024

Conversation

scbedd
Copy link
Member

@scbedd scbedd commented Aug 20, 2024

Resolves #3171

@scbedd scbedd self-assigned this Aug 20, 2024
@scbedd
Copy link
Member Author

scbedd commented Aug 23, 2024

Located a hole in the logic where we don't properly handle when the body doesn't parse even when it's marked as json (this happens for deliberate error cases).

This test in java turned it up. Newest commit protects against the unexpected exception + resolves the test invocation locally.

@scbedd scbedd merged commit c597728 into main Aug 25, 2024
21 checks passed
@scbedd scbedd deleted the real-json-comparison branch August 25, 2024 18:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

[Test-Proxy] Custom matcher for body keys only
3 participants