Skip to content

Tests using jsonPath wrongly use formatted arguments as the expected value #32036

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.

Sign up for GitHub

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

Jump to bottom
Closed
snicoll opened this issue Jan 16, 2024 · 0 comments
Closed

Tests using jsonPath wrongly use formatted arguments as the expected value #32036

snicoll opened this issue Jan 16, 2024 · 0 comments
Assignees
@snicoll
Labels
status: backported An issue that has been backported to maintenance branches type: task A general task
Milestone
6.1.4

Comments

@snicoll
Copy link
Member

snicoll commented Jan 16, 2024

Several tests in our test suite uses the .jsonPath(String expression, Object...args) to evaluate the value of a field at a particular place. Some of these tests are no-op as they use the arguments as the expected value fo the field, see ExceptionHandlerTests for an example.

We should review usage of those tests and use .isEqualTo accordingly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@snicoll snicoll

Labels
status: backported An issue that has been backported to maintenance branches type: task A general task
Projects
None yet
Milestone
6.1.4
Development

No branches or pull requests
1 participant
@snicoll