Skip to main content
Browser profiles save authenticated browser sessions so tests can skip login steps and reuse existing sessions.

​
Why Use Browser Profiles?

Save time - Eliminate 30-60 seconds of login flow from every test Test different roles - Maintain separate profiles for admin, customer, guest users Handle complex auth - Skip 2FA, OAuth, SSO flows after initial setup Persistent state - Keep cookies, localStorage, session data across test runs

​
How Profiles Work

A browser profile captures the complete browser state including:
  • Cookies
  • Local storage
  • Session storage
  • IndexedDB
  • Service workers
When a test uses a profile, it starts with this exact state - as if you had just logged in.

​
Creating a Profile

1

Navigate to Profiles

Go to Profiles → New Profile in the dashboard
2

Name your profile

Click the profile name to edit it. Use descriptive names like:
  • “Admin User”
  • “Premium Customer”
  • “Free Tier User”
  • “Guest User”
Include the user role and environment in the name (e.g., “Admin - Staging”)
3

Start a live session

Click Resume to open a live browser session
The live session runs in a real browser environment where you can interact normally
4

Perform authentication

In the live session:
  • Navigate to your login page
  • Enter credentials
  • Complete 2FA/security checks
  • Navigate through your app as needed
  • Verify you’re fully logged in
Don’t close the browser tab - use the Propolis interface to save
5

Save the profile

Click Save to capture the current browser state
Profile is now ready to use in tests!

​
Using Profiles in Tests

Select your saved profile from the Profile dropdown when creating or viewing a test. The test will start with this profile’s authenticated state, skipping any login steps.
  • New Test
  • Existing Test
  1. Go to Create → Build Step by Step
  2. In test configuration, find Browser Profile
  3. Select your profile from the dropdown
  4. Test starts already authenticated

​
Managing Profiles

​
Live Sessions

When a profile session is active (Resume clicked):
  • View Session - Opens the browser in a new tab to see what’s happening
  • Live Preview - Shows an embedded iframe of the browser
  • Save - Captures current state and closes session
Live sessions remain active until you explicitly save or close them. You can leave them running while you work.

​
Updating Profiles

Sessions expire over time. To update a profile:
  1. Click Resume on the profile
  2. Re-authenticate if session expired
  3. Make any necessary changes
  4. Click Save to update the profile
Set a reminder to refresh profiles periodically (weekly or monthly) to ensure tests don’t fail due to expired sessions.

​
Deleting Profiles

Click the delete icon to remove a profile permanently. Any tests using this profile will start with a fresh browser instead.
Deleting a profile doesn’t delete tests that reference it, but those tests will no longer be authenticated.

​
Troubleshooting

Symptom: Tests using profile still show login pageSolutions:
  • Resume profile and re-authenticate
  • Check if cookies expired
  • Verify application didn’t change auth flow
  • Ensure profile was saved after authentication
Symptom: Test fails partway through with authentication errorsSolutions:
  • Application session timeout is too short
  • Update profile more frequently
  • Check application session settings
  • Consider re-authenticating in long-running tests