Unit testing controllers in NestJS - Performance & Optimization

Performance: Unit testing controllers

LOW IMPACT

Unit testing controllers affects development speed and feedback loop but does not impact runtime page load or rendering performance.

Testing controller logic efficiently without unnecessary dependencies

NestJS

describe('UserController', () => {
  let controller: UserController;
  const mockUserService = { getUser: jest.fn().mockResolvedValue({ id: '1', name: 'Test' }) };
  beforeEach(() => {
    controller = new UserController(mockUserService as any);
  });
  it('should return user data', async () => {
    const result = await controller.getUser('1');
    expect(result).toEqual({ id: '1', name: 'Test' });
  });
});

Mocks dependencies to isolate controller logic, making tests faster and simpler.

📈 Performance Gainruns tests instantly, reduces memory and CPU usage

Testing controller logic efficiently without unnecessary dependencies

NestJS

describe('UserController', () => {
  let controller: UserController;
  beforeEach(async () => {
    const module = await Test.createTestingModule({
      controllers: [UserController],
      imports: [DatabaseModule, HttpModule],
      providers: [UserService],
    }).compile();
    controller = module.get<UserController>(UserController);
  });
  it('should return user data', async () => {
    const result = await controller.getUser('1');
    expect(result).toBeDefined();
  });
});

This loads full modules and dependencies, making tests slower and more resource-intensive.

📉 Performance Costblocks test execution longer, increases memory usage

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Full module loading in tests	0	0	0	[X] Bad
Mocking dependencies in tests	0	0	0	[OK] Good

Rendering Pipeline

Unit testing controllers runs outside the browser and does not affect the browser rendering pipeline.

⚠️ Bottlenecknone

Optimization Tips

1Mock dependencies to isolate controller logic and speed up tests.

2Avoid loading full modules in unit tests to reduce resource use.

3Unit tests do not affect browser rendering or Core Web Vitals.

Performance Quiz - 3 Questions

What is the main performance benefit of mocking dependencies in unit tests for controllers?

A Tests improve browser rendering speed

B Tests run faster by avoiding loading full modules

C Tests reduce network requests during page load

D Tests decrease CSS paint times

DevTools: Performance

How to check: Run tests with a profiler or watch test execution time in terminal or IDE test runner.

What to look for: Look for test duration and CPU usage to identify slow tests caused by heavy dependencies.