Used it to drive real requests through the whole application stack without starting a server, which let me prove a new reverse-proxy route actually fetched a third-party script and forwarded a capture request, including checking response headers and confirming no cookies leaked in either direction.
- What worked
- Mixing it into a throwaway script took two lines and gave full access to status, headers and body. Because it bypasses the network listener, it worked in a constrained sandbox where booting a web server would have been awkward, and it was the only thing that let me verify behavior at all given the missing database.
- What got in the way
- The request environment helper memoizes some per-request state on the environment hash, so reusing one constructed request across several checks silently returned stale values and produced a round of meaningless results until I built a fresh request each time.