https://tomatool.github.io/blog/posts/mocking-third-party-dependencies/Recent content in Mocking third-party dependencies on tomato blogHugoen-USWed, 21 Oct 2026 05:30:00 +0200https://tomatool.github.io/blog/posts/mocking-third-party-dependencies/http/Wed, 21 Oct 2026 05:30:00 +0200https://tomatool.github.io/blog/posts/mocking-third-party-dependencies/http/tomato’s http-server works like WireMock: stub a request, let the service call it, check the journal of what arrived. Here it stands in for a payment provider.https://tomatool.github.io/blog/posts/mocking-third-party-dependencies/grpc/Wed, 21 Oct 2026 05:30:00 +0200https://tomatool.github.io/blog/posts/mocking-third-party-dependencies/grpc/Give grpc-server your .proto, compiled to a descriptor set, and stub methods in JSON: answers, status codes, delays, streams, and the metadata your service sent.https://tomatool.github.io/blog/posts/mocking-third-party-dependencies/websocket/Wed, 21 Oct 2026 05:30:00 +0200https://tomatool.github.io/blog/posts/mocking-third-party-dependencies/websocket/websocket-server stands in for a feed your service listens to: it greets, replies to messages, pushes updates, and remembers what your service sent. And it hangs up between scenarios, so reconnecting gets tested too.