You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately i can't reopen #250 but I ran into the issue again.
The issue is that respx gives a very nice error if a request was issued but not mocked. The problem is that with just this error it is hard to debug what is going on in the code under test. Normally (with pytest), it shows the diff between the actual and expected values of an assert statement, which really helps with debugging.
With respx we only get an error that a specific url was not mocked. But we don't get information on which intercepted requests were successfully mocked and what the difference is. It would be much easier to debug if there was some kind of diff showing all mocked and intercepted requests.
Unfortunately i can't reopen #250 but I ran into the issue again.
The issue is that respx gives a very nice error if a request was issued but not mocked. The problem is that with just this error it is hard to debug what is going on in the code under test. Normally (with pytest), it shows the diff between the actual and expected values of an assert statement, which really helps with debugging.
With respx we only get an error that a specific url was not mocked. But we don't get information on which intercepted requests were successfully mocked and what the difference is. It would be much easier to debug if there was some kind of diff showing all mocked and intercepted requests.
An example would be:
In this case it would be nice to show an error like:
The text was updated successfully, but these errors were encountered: