Browser extension — capture, mock and record right in your browser

The Mockarty extension turns the browser you already debug in into a capture
tool, a mocking proxy and a UI-test recorder. It works without an account:
install it, press record, and everything stays local until you decide to send it
to Mockarty.

Install

1. Take the extension from extension/chrome in the Mockarty repository —
   the folder is ready to load as-is, no build step.
2. Keep the folder where it is — Chrome loads the extension from that path on every start.
3. Open chrome://extensions, turn on Developer mode, click Load
   unpacked and pick the folder.
4. Pin the Mockarty icon to the toolbar. Clicking it opens the side panel.

Works in Chrome, Edge, Brave and other Chromium browsers.

Capture traffic

Open the panel and press Start. Every request the page makes is recorded
with method, URL, status, timing, headers and bodies — including WebSocket
frames in both directions.

• Recording works offline. Captures live in the browser until you send them.
• Secrets are stripped as they are recorded — tokens, cookies, password
  fields and configured JSON paths never reach storage in clear text.
• Press Stop when done, or use the keyboard: Alt+Shift+C.

Each capture can be turned into:

• a Postman collection, a HAR file or a cURL command — no server needed;
• mocks in Mockarty — select the requests and press Create mocks;
• a recorded session in Mockarty, if you are connected.

Mock and modify requests

The Rules section intercepts requests before they leave the browser:

Rules match by URL pattern, method and — for GraphQL — operation name. Responses
support templating: {{faker.email}}, values taken from the request, and
sequential counters.

Bring your existing mocks down from Mockarty. If your team already built
mocks on the server, press Pull mocks — they become local rules and start
answering in your browser immediately. Pulling again updates those rules instead
of duplicating them.

Alt+Shift+R switches all interception off and on — the “make this page normal
again” button.

Record a UI test

Press Record in the Actions tab and use the page normally. Clicks, typing
and navigation are recorded with stable selectors (roles and accessible names
first, generated ids avoided).

Right-click any element while recording to add an assertion: visible, hidden,
has text, has value, attribute, count, or URL.

When you are done:

• Export as Playwright code — a ready .spec.ts you can run anywhere;
• Send to Mockarty — it becomes a UI test you can schedule, run on a fleet
  and attach to a test case.

Audit a page

The Audit tab runs accessibility and performance checks on the current page
and keeps a short history, so you can see whether a change made things better.
No server required.

Connect to Mockarty

Everything above works standalone. Connecting adds: sending captures and tests
to your project, pulling mocks, seeing runs and notifications, and using the
browser as a UI-test runner for your team (see
Run UI tests in your browser).

Three ways to connect:

1. Use my Mockarty session — if you are already signed in to Mockarty in
   this browser, one click exchanges that session for a scoped token.
2. Pairing page — open Mockarty → Connect extension and approve.
3. Manual token — paste an API token and the server URL.

If a request comes back 403, the token is fine but your account has no seat
or permission for that feature — ask an administrator. Re-pairing will not help,
and the extension says so instead of sending you round in circles.

Shortcuts

Rebind them at chrome://extensions/shortcuts.

Privacy and storage

• Captures, rules and recordings live in the browser’s local storage; nothing
  leaves your machine until you send it.
• Secrets are redacted at capture time.
• When the browser’s storage fills up, the oldest captures are dropped and the
  panel tells you — capture keeps running.
• Disconnect clears the token but keeps your local captures.

See also

• Run UI tests in your browser
• UI testing
• Recording traffic