Introduce sessionAttributeDoesNotExist in RequestResultMatchers#23756
Closed
drumonii wants to merge 1 commit into
Closed
Introduce sessionAttributeDoesNotExist in RequestResultMatchers#23756drumonii wants to merge 1 commit into
drumonii wants to merge 1 commit into
Conversation
Similar to attributeDoesNotExist of ModelResultMatchers, sessionAttributeDoesNotExist asserts that the given attributes are null in the HttpSession.
Member
|
For anyone interested in achieving the same goal prior to Spring Framework 5.2.1, please note that this is already possible for a single attribute name using a Hamcrest this.mockMvc.perform(get("/"))
.andExpect(request().sessionAttribute("bogus", is(nullValue()))) |
sbrannen
added a commit
that referenced
this pull request
Oct 23, 2019
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Given the matcher
attributeDoesNotExistofModelResultMatchers, it makes sense for a session attributeResultMatcherequivalent –sessionAttributeDoesNotExistwhich asserts that the given session attributes arenullin theHttpSession.