keploy vs httmock
API and HTTP testing tools compared
keploy records application traffic and replays it as tests with mocks, while httmock intercepts HTTP calls made through Python’s `requests` library and returns configured responses. keploy focuses on recorded integration flows across services; httmock focuses on controlling HTTP responses in tests.
keploy: Record and Replay API Tests and Mocks
Keploy records application traffic and replays it as API and integration tests with mocks for dependent services. It suits developers and QA teams seeking repeatable tests from real usage without changing application code.
httmock: Mock HTTP Requests for Python Tests
httmock is a Python library built on requests for mocking HTTP interactions in tests. It lets you provide conditional or catch-all mocked responses when testing code that calls APIs through requests.
| keploy | httmock | |
|---|---|---|
| Language | Go | Python |
| License | Apache-2.0 | — |
| Stars | 18.5k | 471 |
| Forks | 2.4k | 57 |
| Last analyzed | Oct 3, 2026 | Oct 19, 2026 |
Key differences
- keploy is a Go tool that captures API, database, and streaming interactions; httmock is a Python library for requests-based HTTP calls.
- keploy records traffic at the network layer using eBPF and can replay captured flows; httmock activates request handlers in an `HTTMock` context manager.
- keploy supports tests with recorded mocks for databases, external APIs, and streaming or queue systems; httmock configures HTTP response status, content, headers, and cookies.
- keploy describes generating additional tests from recordings and OpenAPI or Swagger schemas, along with coverage and test reports; httmock describes URL matching and configurable mocked responses.
- keploy is licensed under Apache-2.0; httmock's license is reported as NOASSERTION.
- keploy reports 18.5k stars and 2.4k forks; httmock reports 472 stars and 56 forks.
Choose keploy if you…
- need repeatable integration tests from recorded application traffic.
- want to test flows involving databases, external APIs, or streaming systems without relying on live dependencies.
- plan to use recorded tests in CI or explore its described test generation and coverage reporting.
Choose httmock if you…
- want to test a Python API client that uses `requests` without calling a live service.
- need to control HTTP responses by URL, including status, content, headers, or cookies.
- prefer a focused library for intercepting requests within a test context.
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.