docs: clarify Session Testing behavior and assertion scope #9857
+173
−21
Conversation
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
michalsn
approved these changes
Dec 28, 2025
Member
michalsn
left a comment
michalsn
left a comment
There was a problem hiding this comment.
This is a valuable addition, as it effectively summarizes all the relevant aspects of session testing.
paulbalandan
approved these changes
Dec 28, 2025
neznaika0
suggested changes
Dec 28, 2025
| use Config\Session; | ||
|
|
||
| // Load session config | ||
| $config = new \config(Session::class); |
Contributor
Author
There was a problem hiding this comment.
This code is not mine. It was applied automatically by a linter or Rector.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Description
This pull request introduces a dedicated “Session Testing” section that explains why session-specific testing utilities exist, how the ArrayHandler behaves in the testing environment, and how session state should be asserted correctly depending on the testing approach (unit vs feature/HTTP tests).
The changes also clarify the scope and lifecycle of session assertions, distinguishing between PHPUnit-based assertions for direct session usage and TestResponse session helpers that operate during the HTTP request/response lifecycle.
Finally, this PR improves cross-referencing between existing testing documentation to reduce confusion, avoid incorrect usage patterns, and make session testing behavior more predictable and easier to understand for developers.
See #2014
Checklist: