Network Recorder

QA demo

A synthetic record with four save outcomes, for trying Network Recorder's bug reports. All data is fake, there is no sign-in, no cookies and no analytics, and every request goes to this page's own origin (recorder.aref.run).

Reviewer instructions

  1. Install Network Recorder in Chrome and open this page. No account or sign-in is needed.
  2. Enable capture. Click the toolbar icon, choose Approve this origin, accept Chrome's permission prompt, then turn Capture on. Nothing is recorded before you do this.
  3. Reload this page so response checks are active, and wait until “Loaded” appears below.
  4. Reproduce HTTP 200 with success: false. Click Save rejected. The page says “Something went wrong” even though the server answered HTTP 200. The raw response appears under the table.
  5. Mark bug. Within 30 seconds click the toolbar icon, then Mark bug. The report opens in Chrome's side panel beside this page. With Failures only selected it lists one row: App error · HTTP 200, rule success_false.
  6. Copy for issue. Optionally click Mask path on the row (rec_48213907 becomes :redacted), add a title, then click Copy for issue and paste anywhere to see the Markdown. Download JSON gives the same selection as a file.

Synthetic record

Record ID
rec_48213907 fake ID in the request path: practise masking it
Title
Loaded
Loading…

Test actions

Each button sends POST /api/qa/records/rec_48213907 to this origin, and the server answers as described. The query string carries a fake session token, which the extension never stores.

ActionServer responseExpected in Network RecorderPage received
HTTP 200, {"success": true} OK · HTTP 200
rule success_true
—
HTTP 200, {"success": false} App error · HTTP 200
rule success_false; counted as a failure
—
HTTP 500 HTTP error · HTTP 500
counted as a failure
—
The function drops the connection without sending a response. The hosting proxy answers HTTP 500 (FUNCTION_INVOCATION_FAILED). HTTP error · HTTP 500
hosting proxy's answer, not a browser network error; counted as a failure
—

Loading this page also sends GET /api/qa/records/rec_48213907, expected as OK · HTTP 200. Reset clears this page only; to clear the extension's log use its Settings, then Clear this tab.

About “Dropped connection”: the demo function really does drop the connection, but the hosting platform's proxy turns that into an HTTP 500 response (body FUNCTION_INVOCATION_FAILED), so Network Recorder shows an HTTP error here, not a Network error. A Network error means no HTTP response at all (for example net::ERR_CONNECTION_RESET); this hosted demo cannot produce one, but the extension reports it that way when it happens.

Last raw response

What the server actually sent, independent of the extension.

Click a test action.

Check the API without a browser

curl -i -X POST 'https://recorder.aref.run/api/qa/records/rec_48213907?case=rejected'

Expect HTTP/2 200 and a body starting {"success":false,. The other cases are case=success (200, success:true), case=server-error (500) and case=network. A GET without a query returns the record.

Synthetic data only · no cookies, accounts or analytics · safe to share · Privacy Policy · Support