Cwikius-Spring/spring-security
1
0
Fork 0
mirror of synced 2026-05-22 21:33:16 +00:00
Code Issues Packages Projects Releases Wiki Activity

Polish gh-13575

Browse Source
This commit is contained in:
Steve Riesenberg
2023-09-07 14:07:40 -05:00
parent 3a50c92168
commit 9de717ac7a
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/modules/ROOT/pages/servlet/test/mockmvc/result-handlers.adoc
+1 -1
View File
@@ -8,7 +8,7 @@ In order to use Spring Security's ``ResultHandler``s implementations ensure the
import static org.springframework.security.test.web.servlet.response.SecurityMockMvcResultHandlers.*;
----
==== Exporting the SecurityContext
== Exporting the SecurityContext
Often times we want to query a repository to see if some `MockMvc` request actually persisted in the database.
In some cases our repository query uses the xref:features/integrations/data.adoc[Spring Data Integration] to filter the results based on current user's username or any other property.
docs/modules/ROOT/pages/servlet/test/mockmvc/result-matchers.adoc
+2 -2
View File
@@ -22,7 +22,7 @@ import org.springframework.security.test.web.servlet.response.SecurityMockMvcRes
----
======
=== Unauthenticated Assertion
== Unauthenticated Assertion
At times it may be valuable to assert that there is no authenticated user associated with the result of a `MockMvc` invocation.
For example, you might want to test submitting an invalid username and password and verify that no user is authenticated.
@@ -49,7 +49,7 @@ mvc
----
======
=== Authenticated Assertion
== Authenticated Assertion
It is often times that we must assert that an authenticated user exists.
For example, we may want to verify that we authenticated successfully.