Skip to content

Conversation

@sreekesh93
Copy link
Contributor

@sreekesh93 sreekesh93 commented Oct 11, 2021

Refactor the existing JSONPointer unit test with explicitly mentioning the expected values.

Copy link
Contributor

@johnjaylward johnjaylward left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for the full document compare, it's best to use the JSONObject.similar method:

assertTrue(new JSONObject(EXPECTED_COMPLETE_DOCUMENT).similar(actualObject));

@sreekesh93
Copy link
Contributor Author

sreekesh93 commented Oct 11, 2021

assertTrue(new JSONObject(EXPECTED_COMPLETE_DOCUMENT).similar(actualObject));

Thanks ,Updated the changes

@stleary
Copy link
Owner

stleary commented Oct 12, 2021

What problem does this code solve?
Fixes #590 Need to complete unit tests for JSONPointer

Risks
Low, this only affects the unit tests

Changes to the API?
N/A

Will this require a new release?
No

Should the documentation be updated?
No

Does it break the unit tests?
No

Was any code refactored in this commit?
No

Review status
APPROVED

@stleary
Copy link
Owner

stleary commented Oct 12, 2021

Starting 3 day comment window

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants