Skip to content

About

Browser recorder extensions for capturing HAR files with named BreakTest transactions

Resources

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

39 Commits

Folders and files

Repository files navigation

BreakTest Browser Recorder

Browser extensions for recording Chrome, Microsoft Edge, and Firefox sessions as HAR files with named BreakTest transactions.

The recorder captures requests directly through the browser APIs; it does not use an HTTP proxy. Recordings stay local and can be imported through File > Import HAR... in BreakTest.

These are currently local developer extensions and are not yet published in the browser extension stores.

Install

Clone this repository before following the browser-specific installation guide:

git clone https://github.com/Breaking-IT/breaktest-browser-extension.git

Chrome and Chromium-based Edge use the same files from chrome/. Firefox has a separate implementation in firefox/ because its capture APIs differ from Chromium's DevTools protocol.

During a recording, transactions can be renamed from the Transactions list. When removing a transaction, its requests can be removed too or reassigned to the previous or next transaction. The active transaction remains protected until a newer transaction is started.

WebSocket recording

Chrome, Edge, and Firefox record ws:// and wss:// connections created during recording, including handshake headers/status and incoming/outgoing text and binary messages. BreakTest WebSocket import/playback will be implemented separately.

Chrome and Edge use debugger events. Firefox combines native handshake capture with a hook on the page's WebSocket API; it captures messages from documents and frames, but cannot capture messages from worker-created sockets or raw control frames. Handshakes without message capture are explicitly marked in the HAR.

Each connection is one HAR entry owned by the transaction in which it opened. The handshake appears in the request list immediately; subsequent messages are added to that entry until the connection closes or recording stops. Every message has its own _breaktest.transactionId, based on its capture timestamp, so one connection can carry messages for several transactions. Reassigning a transaction updates its message IDs. Deleting its requests also removes its messages; deleting the opening request removes the entire connection.

See the WebSocket HAR format for message fields, encoding and lifecycle metadata.

Server-sent events (SSE)

Chrome, Edge, and Firefox capture incoming SSE messages from EventSource and fetch responses with Content-Type: text/event-stream. The HTTP HAR entry stores _serverSentEvents, including payload, event name, event ID, receive timestamp, and per-message transaction ID. Named events, multiline data, and split UTF-8 chunks are supported. BreakTest playback is separate from this recorder change.

See the SSE HAR format for completeness and timestamp precision.

Development

Keep the versions in both manifests aligned when releasing a recorder update. After changing an unpacked Chromium extension, reload it on chrome://extensions or edge://extensions. Firefox temporary add-ons can be reloaded from about:debugging#/runtime/this-firefox.

The BreakTest repository pins this repository as its browser-extension submodule so released BreakTest archives continue to include the recorder.

Validate both implementations and create the exact ZIP files accepted by the browser stores:

python3 scripts/validate_extensions.py
python3 scripts/package_extensions.py

Packages and SHA-256 checksums are written to dist/. The Chromium package is used for both Chrome and Microsoft Edge. Store listing copy, permission justifications, and reviewer instructions are maintained under store-listing/.

Security and privacy

HAR recordings can contain credentials, cookies, authorization tokens, personal data, and response content. Record only systems you are authorized to test and review recordings before sharing them.

The recorder processes and exports data locally. It does not upload recordings to a BreakTest service. The recording-data consent is remembered locally and can be reviewed or revoked from Privacy & settings in the recorder. See the full privacy policy.

Completed HARs are staged in browser-local IndexedDB so large exports do not cross extension-message size limits. A staged export is removed after a successful download or explicit discard; abandoned exports are eligible for cleanup after 24 hours.

Please report suspected vulnerabilities privately according to SECURITY.md.

License

BreakTest-owned source and documentation are provided under the BreakTest Community Source License 1.0.

About

Browser recorder extensions for capturing HAR files with named BreakTest transactions

Resources

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages