staging-browser-localhost

To automate staging SSO authentication for localhost testing, you retrieve staging tokens and navigate a headless browser session directly to the SSO callback URL using those tokens. This bypasses manual login by injecting credentials via token-based authentication.

Yes, you can take screenshots and accessibility snapshots of a local app during automated browser testing. Once the headless browser session is authenticated and navigated to the local page, use snapshot and screenshot commands to capture UI behavior.

The best way to test Aircall staging features on localhost is by opening a headless browser session authenticated with staging credentials. This approach retrieves staging tokens and routes them through the SSO callback to ensure a deterministic, isolated testing context.

Using a headless browser is required to run SSO callback workflows for local development in this context. The agent-browser tool relies on a headless session to securely retrieve tokens, navigate the callback URL, and maintain an isolated environment for testing.

An automated localhost browser session may fail to maintain staging authentication if the initial token retrieval or SSO callback navigation is incomplete. You must ensure both the idToken and refreshToken are correctly passed to the callback URL to establish the session.

Yes, staging-browser-localhost supports testing without manual login steps. It eliminates manual intervention by programmatically retrieving staging tokens and executing an SSO callback flow to establish an authenticated headless browser session for local development.