mock-engine

This Skill orchestrates a local mock environment for microservices integration testing via a single Docker Compose command. It automatically starts dependencies like MySQL, Redis, and Kafka, runs health checks, and loads base test data to provide an isolated, reproducible testing infrastructure.

Mocking AWS services and message queues for local development is best handled by orchestrating LocalStack and Kafka via Docker Compose. This approach provides built-in health checks and automated data loading to ensure consistent, isolated testing without relying on shared staging infrastructure.

Loading scenario-specific test data into a Docker Compose mock environment is handled by automated data management features. The system auto-loads base fixtures on startup and supports on-demand scenario data injection to ensure consistent, reproducible test environments for specific business flows.

Yes, this mock environment orchestration tool supports Java and Go SDK integrations. It provides built-in SDKs to help development and QA teams easily connect their applications to the isolated Docker Compose mock services and execute consistent end-to-end integration tests.

Docker Compose local mock environments fail to start due to port conflicts when multiple services attempt to bind to the same host port. This Skill provides built-in troubleshooting guidance with guided steps to resolve common container startup failures, data loading errors, and port conflicts.

Yes, you can use WireMock and MQTT for isolated end-to-end testing without shared staging infrastructure. By orchestrating these services locally via Docker Compose, development and QA teams can quickly spin up isolated mock environments to test business flows independently of limited shared staging services.