0Pricing
NestJS Enterprise Backend APIs · Aula

Testes Unitários e de Ponta a Ponta

Escreva testes unitários eficazes para componentes individuais e testes de ponta a ponta para fluxos completos de API usando Jest e Supertest.

Testes Unitários e de Ponta a Ponta é uma aula grátis de NestJS Enterprise Backend APIs no CoddyKit. Esta é a aula 1 de 6. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de NestJS Enterprise Backend APIs, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de NestJS Enterprise Backend APIs inclui 6 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

Why Test Your NestJS App?

Writing tests is crucial for building robust applications. It helps ensure your code works as expected and prevents regressions when you make changes.

  • Reliability: Confirms features work.
  • Refactoring Confidence: Allows changes without fear.
  • Documentation: Tests show how code should be used.

In NestJS, we often focus on two main types: Unit Tests and End-to-End (E2E) Tests.

Unit Testing: Isolated Checks

Unit tests focus on the smallest testable parts of your application, called 'units'. Think of individual functions, methods, or classes (like a NestJS service).

The goal is to test each unit in isolation, meaning without its external dependencies (like databases, external APIs, or other services). This makes them fast and easy to pinpoint issues.

Jest: Your Testing Buddy

NestJS projects come pre-configured with Jest, a popular JavaScript testing framework. Jest makes writing and running tests straightforward.

You can run your tests directly from your terminal. Let's see a simple example of a Jest test file.

// my-first.spec.ts

describe('Basic Jest Test', () => {
  it('should be true', () => {
    // The 'expect' function is how you assert things
    expect(true).toBe(true);
  });

  it('should compare numbers', () => {
    expect(5).toBeGreaterThan(3);
  });
});

Unit Testing a NestJS Service

Let's test a simple NestJS service that handles user data. We'll use @nestjs/testing to create a test module, allowing us to inject our service and its mocked dependencies.

Here, we're testing a UsersService's findAll() method, ensuring it returns users and interacts correctly with its (mocked) repository.

// users.service.spec.ts
import { Test } from '@nestjs/testing';
import { UsersService } from './users.service'; // Assume this file exists

// Mock the repository to isolate the service
const mockUsersRepo = {
  find: jest.fn(() => Promise.resolve([{ id: 1, name: 'Alice' }])),
};

describe('UsersService Unit Test', () => {
  let service: UsersService;

  beforeEach(async () => {
    const module = await Test.createTestingModule({
      providers: [
        UsersService,
        { provide: 'UserRepository', useValue: mockUsersRepo },
      ],
    }).compile();

    service = module.get<UsersService>(UsersService);
  });

  it('should return an array of users', async () => {
    const result = await service.findAll();
    expect(result).toEqual([{ id: 1, name: 'Alice' }]);
    expect(mockUsersRepo.find).toHaveBeenCalledTimes(1);
  });
});

Mocking for Isolation

Mocking is key in unit testing. It means replacing real dependencies (like a database connection or another service) with controlled, fake versions.

This ensures your test only focuses on the unit itself, not on potential issues in its dependencies. In Jest, jest.fn() creates a mock function you can track and control.

// mock-dependency.spec.ts

const mockLogger = {
  log: jest.fn(), // A mock function
};

class MyComponent {
  constructor(private logger: typeof mockLogger) {}

  doSomething(message: string) {
    this.logger.log(`Doing: ${message}`);
    return `Done: ${message}`;
  }
}

describe('Mocking Example', () => {
  it('should call the mock logger', () => {
    const component = new MyComponent(mockLogger);
    const result = component.doSomething('Hello');

    expect(result).toBe('Done: Hello');
    // Verify the mock function was called with specific arguments
    expect(mockLogger.log).toHaveBeenCalledWith('Doing: Hello');
  });
});

End-to-End (E2E) Testing: Full Flow

While unit tests check small parts, End-to-End (E2E) tests verify the entire system, from the user's perspective. For an API, this means making actual HTTP requests to your running NestJS application.

E2E tests ensure that all components (controllers, services, database, authentication, etc.) work together correctly as a complete flow. They are slower but provide high confidence.

Supertest: API Request Helper

For E2E tests, we need a way to make HTTP requests to our NestJS application. Supertest is a popular library that makes this easy, allowing you to simulate requests and assert on responses.

NestJS's testing utilities integrate well with Supertest, enabling you to spin up a test instance of your application.

E2E Testing a NestJS Controller

Let's write an E2E test for a simple AppController that exposes a GET / endpoint. We'll use @nestjs/testing to create an application instance and supertest to send an HTTP request to it.

This test simulates a client hitting your API and checks the HTTP status code and response body.

// app.e2e-spec.ts
import * as request from 'supertest';
import { Test } from '@nestjs/testing';
import { INestApplication } from '@nestjs/common';
import { AppModule } from './../src/app.module'; // Your main app module

describe('AppController (e2e)', () => {
  let app: INestApplication;

  beforeAll(async () => {
    const moduleFixture = await Test.createTestingModule({
      imports: [AppModule],
    }).compile();

    app = moduleFixture.createNestApplication();
    await app.init(); // Initialize the NestJS app
  });

  it('/ (GET) should return "Hello World!"', () => {
    return request(app.getHttpServer())
      .get('/')
      .expect(200)
      .expect('Hello World!');
  });

  afterAll(async () => {
    await app.close(); // Close the app after tests
  });
});

E2E & Database Management

When running E2E tests, especially those involving databases, you need a strategy for managing test data. This often includes:

  • Dedicated Test Database: Use a separate database instance for tests.
  • Seeding Data: Populate the database with known test data before each test or test suite.
  • Cleaning Up: Clear or reset the database after tests to ensure isolation and prevent test pollution.

This ensures tests are consistent and repeatable.

Quick Check: Testing Types

Consider the following statements about Unit and End-to-End (E2E) testing. Which one is TRUE?

Recap: Unit & E2E Testing

Great job! You've explored the foundations of testing in NestJS:

  • Unit Tests: Focus on isolated components (services, functions), using Jest for fast, precise checks. Mocking is key here.
  • E2E Tests: Validate the entire application flow, from request to response, often using Supertest to simulate HTTP calls. They are slower but provide high confidence in the integrated system.

Both testing types are vital for building reliable and maintainable NestJS applications.

Perguntas Frequentes

A aula “Testes Unitários e de Ponta a Ponta” é grátis?

Sim — o texto completo de “Testes Unitários e de Ponta a Ponta” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de NestJS Enterprise Backend APIs, atualize para CoddyKit PRO. O curso de NestJS Enterprise Backend APIs inclui 6 aulas no total.

O que vou aprender em “Testes Unitários e de Ponta a Ponta”?

Escreva testes unitários eficazes para componentes individuais e testes de ponta a ponta para fluxos completos de API usando Jest e Supertest. Você pratica NestJS Enterprise Backend APIs com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar NestJS Enterprise Backend APIs?

Nenhuma experiência prévia é necessária. NestJS Enterprise Backend APIs no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 1 de 6.

Quanto tempo leva a aula “Testes Unitários e de Ponta a Ponta”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de NestJS Enterprise Backend APIs?

Sim. Cada aula de NestJS Enterprise Backend APIs inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

  1. Testes Unitários e de Ponta a Ponta
  2. Frameworks Hardhat e Truffle
  3. Testes de Desempenho de APIs
  4. Testes unitários de contratos inteligentes
  5. Conteinerização e Kubernetes
  6. Implantação em redes de teste e na rede principal
← Voltar para NestJS Enterprise Backend APIs