RequestFox Add to Chrome

For QA testers: catch the bugs the screen hides

A page can look fine while a call behind it failed, fired twice or returned an error inside a 200 OK. RequestFox watches every call while you test, flags those problems as they happen, ties each one to your click, and turns the session into evidence a developer can act on.

For RequestFox 2.4.0.

History: past recording sessions listed with their call and problem counts, to reopen or compare
Every session is kept in History.

What you will find that the screen does not show

  • Calls that failed quietly while the page kept a stale value.
  • The same request sent twice by one click (a double submit), or retried after a failure.
  • A GraphQL or JSON-RPC error inside a 200 OK.
  • A 401 caused by an expired token, said in words.
  • An answer whose shape changed since earlier in the session.
  • JavaScript errors, next to the calls.

How to record API calls.

Bug reports nobody has to reproduce

Open a GitHub or Linear issue from a call with the repro filled in, or export the session as a self-contained HTML report or a HAR file to attach. Authorization headers, cookies and secret-shaped fields are redacted by default, so the evidence is safe to share.

Test the edge cases without waiting for the backend

Make an endpoint fail, drag or return an empty list, and see what the page does. Calls you changed are labelled, so nobody files them as real bugs. How to mock an API response.

Make a manual check repeatable

Save the calls that matter, add pass/fail checks, chain them into a suite, and hand the suite to CI. How to run API checks in CI.

Try it on your next test run.

Add to Chrome, free Add to Firefox