FAQs
Guides for authoring, running and analysing tests across web automation, API and performance — plus setup, collaboration and release notes.
Recorder/agent FAQs
Common questions about the browser recorder, the Local Agent connection, and running tests locally.
Why isn't the recorder capturing my actions?
Recording is handled by the BitAssert browser extension. If nothing is captured, the extension is disabled, missing permissions on the target site, or out of date. Enable it, grant site access, reload, and start a new recording session.
What browser extension do I need to record, and what permissions?
The BitAssert recorder browser extension, with permission to access the site you're recording. Without those permissions it can't capture actions.
Why is the target site blank in the recorder and won't load?
The recorder loads the site in an embedded frame. Sites that block embedding (via X-Frame-Options or CSP frame-ancestors) refuse to render, leaving the pane blank. This is enforced by the target site — record against a page/environment that allows embedding.
Why does my local run end the moment it starts?
The Local Agent isn't connected. Launch it and confirm the connection indicator before running locally.
How do I know the Local Agent is connected?
The UI shows a connection indicator/status for the agent. If it shows disconnected, the agent isn't running or isn't reachable.
Which browser do I need for local web runs?
Local web runs launch a real Chrome browser, so Chrome must be installed and its version compatible with the bundled driver.
Why does a local run fail to launch the browser (version mismatch)?
If Chrome is missing or its version no longer matches the bundled driver, the session can't be created and the run fails before any step. Update Chrome, restart the Local Agent so it resolves a matching driver, and run again.
The agent is running but the platform can't reach it — why?
The platform connects to the agent over a local WebSocket (default port 8887). If it's running but unreachable, the port is blocked by a firewall/VPN or already in use. Allow the port locally, close any duplicate agent, and restart.
Why won't the agent start ("port already in use")?
Another process — or a second copy of the agent — already holds the port (default 8887). Close the conflicting app/duplicate agent, or start the agent on a different port and use that port from the platform.
Does a firewall, antivirus, or VPN affect the Local Agent?
Yes — security software and some VPNs block local WebSocket connections even when the agent is running. Add an exception for the agent's port or temporarily disconnect the VPN, then reconnect.
Why did my local run drop in the middle?
If the machine sleeps, the network changes, or the agent process closes, the WebSocket disconnects and the live local run is lost (local runs aren't persisted). Keep the machine awake for the run's duration and reconnect before retrying.