BreakTest Browser Recorder

BreakTest Browser Recorder captures HTTP and HTTPS traffic directly through the browser's debugging and web-request APIs. It does not require a proxy. Start recording here without reloading the current page, or start in an incognito/private window. The next-transaction popup automatically increments counters such as UC1_01_ to UC1_02_. BreakTest can turn named transactions into Transaction Controllers when importing HAR. Features: - Records WebSocket handshake headers, incoming/outgoing text and binary messages, and disconnect metadata. - Captures incoming SSE events from EventSource and fetch streams with timestamps, event names, and event IDs. - Tags streaming messages with transaction IDs even when connections span multiple transactions. - Captures the first homepage request in incognito by attaching before the Start URL loads. - Records request and response headers, bodies, timings, and status details. - Assigns requests to named transactions. - Embeds selected/dropped file bytes in a custom HAR upload inventory, including files selected but never submitted (20 MiB per file; 64 MiB per recording). - Shows compact request waterfalls, response sizes, and available timing phases. - Keeps Chrome recording active through initial authentication/navigation errors. - Finds the recording tab using a button or Command+Shift+9 / Ctrl+Shift+9. - Optionally disables browser cache. - Supports incognito/private recording when browser access is enabled. - Exports locally for File > Import HAR... in BreakTest. Embedded files require importer support for the custom upload inventory and are not automatically mapped to individual requests. No empty inventory is added when no files were captured. Recording begins only after you accept the recording-data notice. Consent is remembered locally and can be reviewed or revoked through Privacy & settings. Changed data practices require consent again. The extension does not upload recordings, run analytics, display advertising, or share recorded information. HAR files can contain credentials and personal data; review them before sharing. Chrome and Microsoft Edge use the same Chromium extension. Firefox uses its native response-stream APIs.