How do you test a NestJS microservice controller in isolation without a real message broker?
Create a TestingModule with the controller and mocked service providers. Call the handler methods directly — no NestFactory.createMicroservice(), no broker connection, and no transport is needed. The message pattern decorators are metadata only and do not affect how the method executes when called directly.
- 1
Call handler methods directly — @MessagePattern and @EventPattern decorators are metadata, not runtime wrappers.
- 2
No broker connection is needed — the transport layer is completely irrelevant to handler logic.
- 3
Mock injected services with useValue and jest.fn() — same approach as HTTP controller tests.
- 4
For integration tests that verify the transport, use a test Docker Compose with a real broker.
- 5
Test error paths by making mocked services throw RpcException and asserting the re-thrown exception.
Scenario Questions
0-2 years experience
- 1You need to unit test a NestJS microservice controller that listens to a RabbitMQ pattern, but you don't want to spin up RabbitMQ. How would you set up the test?
- 2What steps would you take to mock the ClientProxy in a NestJS microservice controller test?
2-5 years experience
- 1We added a new message pattern to our NestJS microservice, and the existing controller tests started failing. Walk me through how you'd debug the issue without a real broker.
- 2Explain the trade‑offs between using Nest's TestingModule with a mocked ClientProxy versus using an in‑memory broker like NATS for controller tests.
5-8 years experience
- 1Our system has dozens of microservice controllers, and the CI pipeline is taking too long because each test spins up a mock broker. How would you redesign the testing approach to keep isolation but improve speed and reliability?
- 2When testing a controller that performs complex transformations on incoming messages, what edge cases would you cover, and how would you structure your mocks to avoid false positives at scale?
8+ years experience
- 1Looking ahead, we plan to migrate several services from RabbitMQ to Kafka while keeping the same controller interfaces. How would you evolve our testing strategy to support both brokers without duplicating test code?
- 2Across multiple teams, there’s inconsistency in how microservice controllers are unit‑tested. Propose a reusable testing library or pattern that enforces best practices while allowing team autonomy.
Follow-up Questions
- What assertions would you place on the mock's send method?
- How do you prevent mock state from leaking between test cases?
- Can you sketch the TestingModule setup code for this controller?