Skip to content

[dummy-responder]Configurable Mock Service

Perfect for testing, load testing, and development workflows with HTTP, WebSocket & SSE support

Quick Start โ€‹

Get up and running in seconds:

bash
# Build and run directly
make build
./dummy-responder

# Or use go run
go run ./cmd/dummy-responder
bash
# Using Docker
docker build -t dummy-responder .
docker run -p 8080:8080 dummy-responder

# Using Docker Compose
docker-compose up
bash
# Deploy to Kubernetes
kubectl apply -f k8s-example.yaml

Example Usage โ€‹

bash
# Simple request
curl http://localhost:8080/

# With custom status code and delay
curl "http://localhost:8080/?status=201&delay=2s"

# JSON response with failure simulation
curl "http://localhost:8080/?content-type=json&failure-rate=20"
javascript
const ws = new WebSocket('ws://localhost:8080/ws');
ws.onopen = () => ws.send('Hello Server!');
ws.onmessage = (event) => console.log('Received:', event.data);
javascript
const eventSource = new EventSource('http://localhost:8080/events');
eventSource.onmessage = (event) => {
  console.log('SSE Event:', event.data);
};

What Makes It Special? โ€‹

๐ŸŽฏ Purpose-Built for Testing
Unlike generic mock services, [dummy-responder] is specifically designed for testing scenarios. It provides the exact features you need to simulate various network conditions, response patterns, and failure modes.

๐Ÿ”ง Zero Configuration Required
Works out of the box with sensible defaults, but highly configurable when you need specific behaviors. No complex setup files or external dependencies.

๐Ÿ“ˆ Production-Ready Architecture
Built with Go for performance and reliability using a modular package structure. Includes proper error handling, graceful shutdowns, and essential operational visibility.

๐ŸŒ Modern Web Standards
Supports the latest web technologies including WebSockets for real-time communication and Server-Sent Events for live data streaming.


Ready to start testing? Check out our User Guide or dive into the Developer Documentation.

Released under the MIT License... (see LICENSE.md)