NestJS Enterprise Backend APIs · Lezione

Test unitari ed E2E

Scriva test unitari efficaci per i singoli componenti e test end-to-end per flussi API completi utilizzando Jest e Supertest.

Lezione 1 di 611 passaggi

Test unitari ed E2E è una lezione NestJS Enterprise Backend APIs gratuita su CoddyKit. Questa è la lezione 1 di 6. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento NestJS Enterprise Backend APIs, e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso NestJS Enterprise Backend APIs include 6 lezioni in totale.

Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.

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?

Rispondi nella lezione interattiva

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.

Gratis per iniziare

Impara TypeScript con un tutor IA — gratis

Scrivi ed esegui vero codice nel tuo browser, ricevi aiuto istantaneo da un tutor IA disponibile 24/7, e riprendi da dove hai lasciato sul web o nell'app.

Corsi: 20
Lezioni: 76

Inizia a imparare gratis Visualizza il corso completo

Domande Frequenti

La lezione «Test unitari ed E2E» è gratuita?

Sì — il testo completo di «Test unitari ed E2E» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso NestJS Enterprise Backend APIs, passa a CoddyKit PRO. Il corso NestJS Enterprise Backend APIs include 6 lezioni in totale.

Cosa imparerò in «Test unitari ed E2E»?

Scriva test unitari efficaci per i singoli componenti e test end-to-end per flussi API completi utilizzando Jest e Supertest. Eserciti NestJS Enterprise Backend APIs con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.

Ho bisogno di esperienza per iniziare NestJS Enterprise Backend APIs?

Non è richiesta alcuna esperienza precedente. NestJS Enterprise Backend APIs su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 1 di 6.

Quanto tempo richiede la lezione «Test unitari ed E2E»?

La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.

Posso scrivere ed eseguire codice in questa lezione NestJS Enterprise Backend APIs?

Sì. Ogni lezione NestJS Enterprise Backend APIs include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.

Tutte le lezioni di questo corso

← Torna a NestJS Enterprise Backend APIs