Set session storage
The Set session storage step allows you to programmatically define browser session storage values during your tests.
Session storage is commonly used by modern web applications to hold temporary data such as authentication state, feature flags, UI preferences, or environment-specific settings. By setting these values directly, you can control how your application behaves without needing to recreate the full user journey every time.
Control application state instantly
Instead of navigating through multiple steps to reach a specific state, you can inject the required session storage values directly.
This is useful for:
Simulating logged-in states
Enabling or disabling feature flags
Pre-configuring user preferences
Reproducing edge-case scenarios
Testing fallback or error states
This reduces unnecessary steps while keeping your tests clear and intentional.
Use dynamic and stored values
Session storage values can be populated using:
Static values
Values from the DoesQA Value Store
Data passed in via CI/CD
Values returned from API calls
Outputs from custom code nodes
This makes the step highly flexible and suitable for complex, environment-driven testing strategies.
Improve speed without reducing coverage
Setting session storage directly can:
Reduce repetitive setup steps
Speed up regression runs
Minimise dependency on UI flows
Enable deeper state-based testing
You are not skipping validation. You are controlling state deliberately.
Works alongside state management steps
Set session storage pairs naturally with:
Delete session storage
Check session storage
Browser reload
Authentication and MFA flows
Together, these tools give you full control over client-side state inside your automation.
Precise state control leads to faster tests and more reliable outcomes.