responses vs python-mocket
Python network mocking tools for tests compared
responses and python-mocket both let Python tests simulate network interactions without relying on live services. responses focuses on mocking calls made with `requests`, while python-mocket patches socket and SSL behavior to cover a broader range of clients and protocols.
responses: Mock Python Requests in Tests
Responses intercepts Python Requests calls and serves registered mock responses, so tests can exercise HTTP client code without contacting real services. It supports request matching, callbacks, call assertions, and ordered response sequences.
python-mocket: Mock Socket Traffic for Python Tests
Mocket lets Python developers intercept socket and SSL traffic so tests can mock HTTP and other protocol clients without making real network requests. It supports synchronous and asynchronous clients, strict network blocking, and custom socket-level mocks.
| responses | python-mocket | |
|---|---|---|
| Language | Python | Python |
| License | Apache-2.0 | BSD-3-Clause |
| Stars | 4.3k | 311 |
| Forks | 386 | 51 |
| Last analyzed | Oct 3, 2026 | Oct 3, 2026 |
Key differences
- responses targets the `requests` library; python-mocket works at the socket and SSL level and supports HTTP as well as lower-level protocols.
- responses offers matchers for request data and headers, ordered response sequences, call assertions, and callbacks; python-mocket offers strict network blocking, socket exceptions, and custom socket-protocol mocks.
- python-mocket describes support for asyncio clients, including aiohttp; responses is presented as a mock for Python `requests`.
- responses is licensed under Apache-2.0; python-mocket is licensed under BSD-3-Clause.
- responses requires Python 3.8 or newer and `requests` 2.30.0 or newer, according to its README. python-mocket's README describes Python 2.7 compatibility as ending at version 3.9.4, with interpreter support varying by version.
- Both projects support recording traffic for reuse: responses records responses to YAML and labels recording and replay beta, while python-mocket records socket traffic to JSON files.
Choose responses if you…
- need focused mocks for code using Python `requests`.
- want request matchers, call-count assertions, or ordered responses for testing changing server behavior.
- prefer to activate mocks with a decorator, context manager, or explicit start and stop calls.
Choose python-mocket if you…
- need to mock socket traffic for HTTP, HTTPS, or a custom protocol client.
- want strict mode to block unmocked network access or simulate socket errors.
- test asyncio clients or need its low-level socket-mocking framework.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.