How do you test a NestJS microservice controller in isolation without a real message broker?

Q: How do you test a NestJS microservice controller in isolation without a real message broker?

describe('OrdersController', () => { let controller: OrdersController; let ordersService: jest.Mocked ; beforeEach(async () => { const module = await Test.createTestingModule({ controllers: [OrdersController], providers: [ { provide: OrdersService, useValue: { create: jest.fn(), findOne: jest.fn(), process: jest.fn(), }, }, ], }).compile(); controller = module.get(OrdersController); ordersService = module.get(OrdersService); }); it('@MessagePattern create_order returns created order', async () => { const dto = { userId: 1, items: [{ productId: 1, qty: 2 }] }; const order = { id: 1, ...dto, status: 'PLACED' }; ordersService.create.mockResolvedValue(order as any); // Call the handler method directly — no transport needed const result = await controller.createOrder(dto as any); expect(result).toEqual(order); expect(ordersService.create).toHaveBeenCalledWith(dto); }); it('@EventPattern order_placed processes the event', async () => { const event = { orderId: '123', items: [] }; await controller.handleOrderPlaced(event as any); expect(ordersService.process).toHaveBeenCalledWith(event); }); }); Call handler methods directly — @MessagePattern and @EventPattern decorators are metadata, not runtime wrappers. No broker connection is needed — the transport layer is completely irrelevant to handler logic. Mock injected services with useValue and jest.fn() — same approach as HTTP controller tests. For integration tests that verify the transport, use a test Docker Compose with a real broker. Test error paths by making mocked services throw RpcException and asserting the re-thrown exception.

Difficulty: 6/10

NestJS testing, microservice controllers, mocking message brokers

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.

Microservice controller unit test without a broker

Microservice controller testing strategy:

1
Call handler methods directly — @MessagePattern and @EventPattern decorators are metadata, not runtime wrappers.

How do you test a NestJS microservice controller in isolation without a real message broker?

Difficulty: 6/10

NestJS testing, microservice controllers, mocking message brokers

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.

Microservice controller unit test without a broker

Microservice controller testing strategy:

1
Call handler methods directly — @MessagePattern and @EventPattern decorators are metadata, not runtime wrappers.

How do you test a NestJS microservice controller in isolation without a real message broker?

How do you test a NestJS microservice controller in isolation without a real message broker?

Scenario Questions

Follow-up Questions