How do I mock a REST API with Moco?

Define REST endpoints in a JSON configuration file specifying request methods, paths, and responses, then run the standalone server. The REST API documentation provides detailed examples for setting up various scenarios beyond basic HTTP stubs.

Moco vs WireMock: which one should I choose?

Moco is simpler and easier to set up with JSON configuration, ideal for quick stubbing and minimal setup. WireMock offers more features like record-and-playback and a richer API, but has a steeper learning curve. Choose based on your need for simplicity versus advanced mocking capabilities.

How can I handle dynamic responses in Moco?

Use Moco's programmatic APIs in Java to create dynamic responses, or extend the framework with custom code. While JSON configuration is static, the Extend Moco section allows for more flexible, logic-driven mocking if needed.

Is Moco suitable for WebSocket testing?

Yes, Moco has dedicated WebSocket APIs that allow you to mock WebSocket endpoints for testing real-time communication. The WebSocket API documentation includes examples for setting up and interacting with WebSocket stubs.

Can I run Moco in a Docker container for CI/CD?

Yes, since Moco is a standalone JAR, you can package it in a Docker image and run it with command-line options. This makes it easy to integrate into CI/CD pipelines for automated integration testing, as suggested in the Command Line Usages.

What are the performance implications of using Moco?

Moco is designed for development and testing, not production loads. It's lightweight but may not handle high concurrency as efficiently as optimized servers; for performance testing, consider more robust tools or ensure proper configuration for your needs.

Moco — Lightweight Java HTTP Stub Server

What is Moco?

Moco is a Java-based stub server framework that allows developers to quickly create mock HTTP, REST, and WebSocket servers for integration testing. It solves the problem of cumbersome stub server deployment by providing a lightweight, configuration-driven approach that replaces traditional WAR file setups.

Target Audience

Java developers and QA engineers who need to mock external HTTP services, REST APIs, or WebSocket endpoints for integration, contract, or end-to-end testing.

Value Proposition

Developers choose Moco for its dead-simple setup, standalone runner, and flexible configuration—enabling rapid creation of stub servers without the complexity of application servers or boilerplate code.

Easy Setup Stub Server

Use Cases

Best For

Mocking REST APIs during frontend or mobile app development
Creating HTTP stubs for integration tests in CI/CD pipelines
Simulating third-party web service dependencies for testing
Testing WebSocket interactions without a live backend
Prototyping API responses before backend implementation
Running lightweight stub servers locally for development

Not Ideal For

Projects requiring complex, stateful mock servers with programmable logic that changes during test execution
Teams working primarily in non-Java ecosystems who prefer language-native mocking tools (e.g., Python's pytest-mock or Node.js's nock)
Scenarios demanding a graphical interface for managing and visualizing stubs without relying on configuration files
High-performance load testing where optimized stub servers with minimal overhead are critical

Pros & Cons

Pros

Easy Setup

Moco allows running a standalone server with a simple JSON configuration file, eliminating the need for complex deployment or application servers, as demonstrated in the Quick Start section with the 'java -jar' command.

Multiple Protocol Support

It supports stubbing for HTTP, REST, WebSocket, and raw socket APIs, providing versatility for different integration testing needs, as listed in the Key Features.

Flexible Configuration

Mock responses can be defined using JSON or programmatic APIs, offering both declarative and imperative approaches, which is highlighted in the Key Features and linked documentation.

Extensible Design

If built-in features are insufficient, Moco can be extended with custom APIs, allowing developers to tailor it to specific requirements, as mentioned in the Extend Moco section of the README.

Cons

Java Dependency

Running Moco requires a JVM, which adds overhead and complexity for teams not already using Java in their stack, as it's a Java-based framework with a standalone JAR.

Static Configuration Limitations

Mock behaviors are primarily defined in static configuration files, making it challenging to create dynamic, stateful stubs without writing custom extensions or code, unlike more programmable alternatives.

Limited Tooling Ecosystem

Compared to alternatives like WireMock, Moco has a smaller community and fewer third-party integrations or tools, which might limit support for advanced features or integrations in diverse environments.

What is Moco?

Target Audience

Java developers and QA engineers who need to mock external HTTP services, REST APIs, or WebSocket endpoints for integration, contract, or end-to-end testing.

Value Proposition

Use Cases

Best For

Mocking REST APIs during frontend or mobile app development
Creating HTTP stubs for integration tests in CI/CD pipelines
Simulating third-party web service dependencies for testing
Testing WebSocket interactions without a live backend
Prototyping API responses before backend implementation
Running lightweight stub servers locally for development

Not Ideal For

Projects requiring complex, stateful mock servers with programmable logic that changes during test execution
Teams working primarily in non-Java ecosystems who prefer language-native mocking tools (e.g., Python's pytest-mock or Node.js's nock)
Scenarios demanding a graphical interface for managing and visualizing stubs without relying on configuration files
High-performance load testing where optimized stub servers with minimal overhead are critical

Pros & Cons

Pros

Easy Setup

Multiple Protocol Support

It supports stubbing for HTTP, REST, WebSocket, and raw socket APIs, providing versatility for different integration testing needs, as listed in the Key Features.

Flexible Configuration

Mock responses can be defined using JSON or programmatic APIs, offering both declarative and imperative approaches, which is highlighted in the Key Features and linked documentation.

Extensible Design

If built-in features are insufficient, Moco can be extended with custom APIs, allowing developers to tailor it to specific requirements, as mentioned in the Extend Moco section of the README.

Cons

Java Dependency

Running Moco requires a JVM, which adds overhead and complexity for teams not already using Java in their stack, as it's a Java-based framework with a standalone JAR.

Static Configuration Limitations

Limited Tooling Ecosystem

Moco

What is Moco?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

Moco

What is Moco?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?