A Ruby test can launch a browser that makes its own AJAX calls. An HTTP recorder attached to Ruby's client libraries does not automatically observe connections opened by that separate browser process.

A browser-facing recording proxy sits on the path those requests use:

browser → recording forward proxy → external service
browser → recording forward proxy → recorded response

Puffing Billy supplies this arrangement for Ruby browser tests. Use its integration for the chosen browser driver, then define the responses or persistent recordings required by the scenario.

Match the actual request, including its method and the URL representation expected by the proxy. The documented HTTPS stub form includes the explicit port, such as https://api.example:443/status.

Choose what happens to an unmatched request. Letting it reach the live service makes one kind of test; rejecting it when no recording exists gives an offline scenario a clearer boundary. Keep recordings specific enough that different submitted bodies do not accidentally receive one canned answer.

For a remote browser, the proxy listener must be reachable from that browser's machine or container. Localhost in the test runner's process does not identify the same listener from a different host.

Tënë sô zo