Jonas Lundberg

Hmm, that should work 🤔 Could you provide a failing test example for the first mock with the querystring.

I tried your reproduced setup, but modified the failing test to mock the same url as in `send_request`, i.e. `https://example.com?...`, and then both tests works. Anything I'm missing?

Doesn't seem to be any problem .. please re-open if there's still an issue.

Sounds like a reasonable feature .. we'll need to dig in httpx to figure out how to best construct a response with the cookies, e.g. `Set-Cookie` headers or other way

@phha I finally got around and implemented a feature for this 😅. Please try the PR out locally, if possible, to rule out any bugs.

Do you mean show all existing/added mock routes that didn't match the request?

In your example you only have 1 mocked route per test case, e.g. `respx_mock.get(url=url + '/hey').respond(status_code=200)` A common pattern is to have a respx mock router that holds all available...

Fair enough. Currently we're relying on the `httpx` representation of their `Request` instance .. https://github.com/lundberg/respx/blob/58ad17e9cee2ea81183a5855acbf4bf45dc9faa0/respx/router.py#L250 To print more details about the actual request, we'll need to write our own httpx...

IMO content/stream is not suited for output since it can be "whatever" and potentially give problems, e.g. binary, multipart, encoding, streaming etc. > Do not like accessing the stream data...

The "all mocked assertion" means that respx is active and configured to require every httpx request to match respx mock route, i.e. the request above (https://our.partner.example.com/their/webhook) does not match any...