-
Notifications
You must be signed in to change notification settings - Fork 38.3k
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
Introduce soft assertions for MockMvc #26917
Conversation
4362294
to
2df94a6
Compare
spring-test/src/main/java/org/springframework/test/web/servlet/ResultMatcher.java
Outdated
Show resolved
Hide resolved
2329c2d
to
c167134
Compare
@nguyensach I've applied your suggestions. Do you need any action on my side? |
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.
LGTM 🚀
spring-test/src/main/java/org/springframework/test/web/servlet/ResultMatcher.java
Outdated
Show resolved
Hide resolved
c167134
to
5e7c51a
Compare
Co-authored-by: Sach Nguyen <[email protected]> It happens very often that MockMvc is used in heavyweight integration tests. It's no use to waste time to check if another condition has been fixed or not. Soft assertion could help a lot to check all conditions at once even if one of them fail.
5e7c51a
to
438c40b
Compare
Current work on this issue can be seen in the following feature branch: main...sbrannen:issues/gh-26917-MockMvc-soft-assertions |
It happens very often that MockMvc is used in heavyweight integration tests. It's no use to waste time to check if another condition has been fixed or not. Soft assertions help a lot by checking all conditions at once even if one of them fails. See spring-projectsgh-26917 Co-authored-by: Sach Nguyen <[email protected]>
It happens very often that MockMvc is used in heavyweight integration tests. It's no use to waste time to check if another condition has been fixed or not. Soft assertions help a lot by checking all conditions at once even if one of them fails. See spring-projectsgh-26917 Co-authored-by: Sach Nguyen <[email protected]>
Thanks for the PR, @wyhasany! 👍 This has been merged into In the end we decided to introduce a new |
It happens very often that MockMvc is used in heavyweight integration tests. It's no use to waste time to check if another condition has been fixed or not. Soft assertions help a lot by checking all conditions at once even if one of them fails. See spring-projectsgh-26917 Co-authored-by: Sach Nguyen <[email protected]>
It happens very often that MockMvc is used in
heavyweight integration tests. It's no use to waste
time to check if another condition has been fixed or
not. Soft assertion could help a lot to check all
conditions at once even if one of them fail.