inline-snapshot
pytest_httpx
| inline-snapshot | pytest_httpx | |
|---|---|---|
| 1 | 1 | |
| 335 | 320 | |
| - | - | |
| 8.8 | 7.4 | |
| 10 days ago | 21 days ago | |
| Python | Python | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
inline-snapshot
pytest_httpx
-
Tips to prevent adoption of your API
I avoid writing automated tests that hit an external API - especially one out of my control - because I don't want my CI runs to ever fail because someone else's service wasn't responding. I want CI to be a completely closed box, such that any failures mean there's a bug in my code.
If I want to test external APIs I'll do that in a separate set of integration tests which are run as part of a separate system, not as part of my CI for every code commit to my repo.
I mostly use Python, and the APIs I talk to are mostly accessed via the requests or httpx libraries - both of which have excellent libraries for productive mocking:
- https://requests-mock.readthedocs.io/en/latest/pytest.html
- https://github.com/Colin-b/pytest_httpx
What are some alternatives?
respx - Mock HTTPX with awesome request patterns and response side effects 🦋
hook-slinger - A generic service to send, retry, and manage webhooks
httpx-cache - Simple caching transport for httpx
pytest-sugar - a plugin for py.test that changes the default look and feel of py.test (e.g. progressbar, show tests that fail instantly)
gomega - Ginkgo's Preferred Matcher Library