MockArraySessionStorage
class MockArraySessionStorage implements SessionStorageInterface
MockArraySessionStorage mocks the session for unit tests.
No PHP session is actually started since a session can be initialized and shutdown only once per PHP execution cycle.
When doing functional testing, you should use MockFileSessionStorage instead.
Properties
protected string | $id | ||
protected string | $name | ||
protected bool | $started | ||
protected bool | $closed | ||
protected array | $data | ||
protected MetadataBag | $metadataBag | ||
protected array|SessionBagInterface[] | $bags |
Methods
No description
Starts the session.
Regenerates id that represents this storage.
Returns the session ID.
Sets the session ID.
Returns the session name.
Sets the session name.
Force the session to be saved and closed.
Clear all session data in memory.
Gets a SessionBagInterface by name.
Checks if the session is started.
Gets the MetadataBag.
Generates a session ID.
No description
Details
bool
regenerate(bool $destroy = false, int $lifetime = null)
Regenerates id that represents this storage.
This method must invoke session_regenerate_id($destroy) unless this interface is used for a storage object designed for unit or functional testing where a real PHP session would interfere with testing.
Note regenerate+destroy should not clear the session data in memory only delete the session data from persistent storage.
Care: When regenerating the session ID no locking is involved in PHP's session design. See https://bugs.php.net/bug.php?id=61470 for a discussion. So you must make sure the regenerated session is saved BEFORE sending the headers with the new ID. Symfony's HttpKernel offers a listener for this. See Symfony\Component\HttpKernel\EventListener\SaveSessionListener. Otherwise session data could get lost again for concurrent requests with the new ID. One result could be that you get logged out after just logging in.
save()
Force the session to be saved and closed.
This method must invoke session_write_close() unless this interface is used for a storage object design for unit or functional testing where a real PHP session would interfere with testing, in which case it should actually persist the session data if required.