Mocking providers in NestJS - Performance & Optimization

Performance: Mocking providers

MEDIUM IMPACT

This concept affects the speed and responsiveness of unit tests by controlling how dependencies are simulated during testing.

Testing a service with dependencies

NestJS

const mockService = { fetchData: jest.fn().mockResolvedValue('mocked data') };
const moduleRef = await Test.createTestingModule({
  providers: [
    DependentService,
    { provide: RealService, useValue: mockService },
  ],
}).compile();

const service = moduleRef.get(DependentService);
await service.callRealDependency();

Mocks replace real calls with fast, predictable responses, speeding up tests and isolating logic.

📈 Performance Gainreduces test runtime by avoiding real network/database calls

Testing a service with dependencies

NestJS

const moduleRef = await Test.createTestingModule({
  providers: [RealService, DependentService],
}).compile();

const service = moduleRef.get(DependentService);
await service.callRealDependency();

Using real providers triggers actual service logic, causing slower tests and possible side effects.

📉 Performance Costblocks test execution longer due to real network or database calls

Performance Comparison

Pattern	Dependency Calls	Test Runtime	Resource Usage	Verdict
Using real providers	Triggers real network/database calls	Longer due to real operations	High due to external resources	[X] Bad
Using mocked providers	Simulates calls with fast responses	Shorter due to no real calls	Low, no external resource usage	[OK] Good

Rendering Pipeline

Mocking providers does not affect browser rendering but impacts the test execution pipeline by replacing real dependencies with mocks to reduce runtime and resource usage.

→Test Setup

→Dependency Injection

→Test Execution

⚠️ BottleneckReal service calls during test execution cause delays and resource consumption.

Optimization Tips

1Always mock external dependencies to speed up tests.

2Avoid real network or database calls in unit tests.

3Use Jest mocks or custom providers to simulate services.

Performance Quiz - 3 Questions

What is the main performance benefit of mocking providers in NestJS tests?

A Improved browser rendering speed

B Faster test execution by avoiding real service calls

C Reduced bundle size in production

D Better CSS selector performance

DevTools: Node.js Profiler or Jest --runInBand with --detectOpenHandles

How to check: Run tests with profiling enabled and observe time spent in dependency calls; check for open handles or slow network/database calls.

What to look for: Long test durations or open handles indicate real calls; fast, isolated tests indicate effective mocking.