How do I mock JSON API responses with httpmock in Rust?

Use methods like `json_body` or `json_body_eq` to set JSON responses and matchers. The library integrates with serde for seamless JSON handling, as mentioned in the built-in helpers for JSON matching.

httpmock vs mockito: which is better for Rust HTTP testing?

httpmock offers more features like standalone server, advanced matching, and fault simulation, making it ideal for complex integration tests. Mockito is simpler and in-memory, better for lightweight unit tests without external dependencies.

Can httpmock simulate slow network connections for testing?

Yes, it includes fault simulation features to add network delays, allowing you to test how your application handles latency and timeouts, as highlighted in the fault simulation capability.

How to use httpmock with async/await in Rust tests?

httpmock provides both synchronous and asynchronous APIs. Use the async methods or wrap calls in async contexts, supported by its fully asynchronous core, ensuring compatibility with async Rust codebases.

Does httpmock support mocking HTTPS endpoints?

Yes, HTTPS support is included, enabling you to mock secure connections without modifying your application's HTTPS handling, as noted in the features list.

How to define reusable mocks with YAML files in httpmock?

You can specify mock configurations in YAML files for reuse across tests. Load them using the file-based mock specification feature, which simplifies managing complex or repetitive test scenarios.

httpmock — Rust HTTP Mocking Library

What is httpmock?

httpmock is a comprehensive HTTP mocking library for Rust designed to simplify testing of applications that rely on external HTTP services. It provides a lightweight mock server that can simulate real HTTP responses, enabling developers to write reliable and isolated tests without depending on live endpoints.

Target Audience

Rust developers writing integration or unit tests for applications that make HTTP requests to external APIs or services, such as web clients, microservices, or API consumers.

Value Proposition

Developers choose httpmock for its expressive, fluent API combined with powerful features like advanced request matching, fault simulation, and detailed verification tools, making it both easy to use for simple cases and capable of handling complex testing scenarios.

HTTP mocking library for Rust

Use Cases

Best For

Testing Rust applications that integrate with third-party HTTP APIs without hitting live endpoints.
Simulating network failures, delays, or HTTP errors to test application resilience and error handling.
Writing integration tests for microservices or distributed systems that require isolated HTTP communication.
Recording and replaying HTTP interactions with external services for consistent test execution.
Defining reusable mock configurations via YAML files for complex or repetitive test scenarios.
Running a standalone mock server via Docker for integration testing in CI/CD pipelines or across different services.

Not Ideal For

Projects that only need simple, in-memory HTTP mocks without a standalone server for unit testing.
Testing non-HTTP network protocols like gRPC, WebSockets, or raw TCP connections.
Environments with strict resource constraints where running an additional mock server process is prohibitive.
Teams preferring zero-dependency mocking solutions that integrate directly into test runners without external setup.

Pros & Cons

Pros

Expressive Fluent API

Provides a chainable, intuitive API for defining mocks, as shown in the example with `when.method(GET).path(...).query_param(...)`, making test code readable and maintainable.

Advanced Request Matching

Built-in support for regex, JSON, cookies, and custom matchers allows precise control over mock expectations, reducing false positives in complex tests.

Standalone and Docker Support

Can run as a separate mock server with an official Docker image, enabling integration testing across services or in CI/CD pipelines without code changes.

Fault Simulation and Verification

Features like network delay simulation and detailed error diffs help test application resilience and debug mismatched requests efficiently, as highlighted in the verification tools.

Cons

Server Overhead

Running a lightweight mock server adds process and resource overhead compared to purely in-memory mocking libraries, which can slow down test execution for simple cases.

HTTP-Only Limitation

Focused solely on HTTP, so it cannot mock other network protocols like gRPC or WebSockets without additional tools or workarounds.

Setup Complexity for Advanced Features

Features like file-based mocks and standalone mode require additional configuration, such as YAML parsing or Docker setup, increasing initial setup time.

Frequently Asked Questions

What is httpmock?

Target Audience

Rust developers writing integration or unit tests for applications that make HTTP requests to external APIs or services, such as web clients, microservices, or API consumers.

Value Proposition

Use Cases

Best For

Testing Rust applications that integrate with third-party HTTP APIs without hitting live endpoints.
Simulating network failures, delays, or HTTP errors to test application resilience and error handling.
Writing integration tests for microservices or distributed systems that require isolated HTTP communication.
Recording and replaying HTTP interactions with external services for consistent test execution.
Defining reusable mock configurations via YAML files for complex or repetitive test scenarios.
Running a standalone mock server via Docker for integration testing in CI/CD pipelines or across different services.

Not Ideal For

Projects that only need simple, in-memory HTTP mocks without a standalone server for unit testing.
Testing non-HTTP network protocols like gRPC, WebSockets, or raw TCP connections.
Environments with strict resource constraints where running an additional mock server process is prohibitive.
Teams preferring zero-dependency mocking solutions that integrate directly into test runners without external setup.

Pros & Cons

Pros

Expressive Fluent API

Provides a chainable, intuitive API for defining mocks, as shown in the example with `when.method(GET).path(...).query_param(...)`, making test code readable and maintainable.

Advanced Request Matching

Built-in support for regex, JSON, cookies, and custom matchers allows precise control over mock expectations, reducing false positives in complex tests.

Standalone and Docker Support

Can run as a separate mock server with an official Docker image, enabling integration testing across services or in CI/CD pipelines without code changes.

Fault Simulation and Verification

Features like network delay simulation and detailed error diffs help test application resilience and debug mismatched requests efficiently, as highlighted in the verification tools.

Cons

Server Overhead

Running a lightweight mock server adds process and resource overhead compared to purely in-memory mocking libraries, which can slow down test execution for simple cases.

HTTP-Only Limitation

Focused solely on HTTP, so it cannot mock other network protocols like gRPC or WebSockets without additional tools or workarounds.

Setup Complexity for Advanced Features

Features like file-based mocks and standalone mode require additional configuration, such as YAML parsing or Docker setup, increasing initial setup time.

Frequently Asked Questions

httpmock

What is httpmock?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

httpmock

What is httpmock?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?