search

jamielennox / requests-mock

Mocked responses for the requests library
https://requests-mock.readthedocs.io
Apache License 2.0
447 stars 71 forks source link

question: difference with "responses" package #213

Open beliaev-maksim opened 2 years ago

beliaev-maksim commented 2 years ago

Hi guys, I wanted to ask you what is the main difference between the current package and https://github.com/getsentry/responses ?

it looks like mocking is performed on the same. From the first glance libs look to be very similar

soxofaan commented 1 year ago

same question here: https://github.com/getsentry/responses/issues/182

beliaev-maksim commented 1 year ago

same question here: getsentry/responses#182

that one is very old.

But comparing projects in 2022-2023 I do not see what requests-mock can do what responses cannot or a fundamental difference. Thus, I asked if authors can provide with some hints

jamielennox commented 1 year ago

Both projects were launched around about the same time when at least for me httpretty was really the only option in python and there were some significant problems with it (like python3 support, inconsistencies etc). Had responses existed we may not have bothered with requests-mock but particularly in OpenStack at the time there was need to do (for example) specific failure testing that was difficult.

To my understanding they do a very similar thing, but I really haven't used responses.

Years ago when i last looked i found (IMO) that the way you matched requests, and the way you craft the response payload was much more flexible in requests-mock. I don't know if that's still true and at this point it's probably a matter of preference.

responses is a better name for a library, but requests-mock definitely gets the SEO boost :)