nestjs-testing
/nestjs-testing
Pisze testy jednostkowe i E2E w NestJS z Jest i supertest, wraz ze strategiami mockowania i izolacją bazy danych.
- Autor
- HoangNguyen0403 ↗
- Repozytorium
- agent-skills-standard ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 22.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 5
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 22.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Pisze testy jednostkowe i E2E w NestJS z Jest i supertest, wraz ze strategiami mockowania i izolacją bazy danych.
Oryginalny opis (EN)
Write Unit and E2E tests with Jest, mocking strategies, and database isolation in NestJS. Use when writing NestJS unit tests, E2E tests with supertest, or mock providers.
Jak działa
- Priority: P2 (MEDIUM)
- Core Rule Anchors
- Structure
- Unit Testing
- E2E Testing
- Strict TypeScript (MANDATORY)
- Anti-Patterns
- References
Podgląd SKILL.md
---
name: nestjs-testing
description: Write Unit and E2E tests with Jest, mocking strategies, and database isolation in NestJS. Use when writing NestJS unit tests, E2E tests with supertest, or mock providers.
metadata:
triggers:
files:
- '**/*.spec.ts'
- 'test/**/*.e2e-spec.ts'
- 'Test.createTestingModule'
keywords:
- supertest
- jest
- beforeEach
---
# NestJS Testing
## **Priority: P2 (MEDIUM)**
## Core Rule Anchors
- **`[BE-TEST-01]` Parameterized Tests for Equivalent Cases**: Prefer `test.each` when methods have multiple equivalent inputs or boundary permutations. Distinct scenarios may stay separate test functions. Reviewers must not demand parameterized rewrites without a behavioral gap.
- **`[BE-TEST-02]` Ban on Brittle DB Mock String Matching**: Do not use string-matching mocks for raw SQL queries. Test pure domain calculations directly, or use a real test DB for repository verification.
- **`[BE-TEST-03]` Ban on Shallow Assertions**: Never assert only `expect(res).toBeDefined()` without inspecting payload fields, status codes, and invariants.
- **`[BE-TEST-04]` Ban on Pass-Through Interface Mocks**: Repositories and service handlers must test contract compliance and error mapping. Ban 1:1 pass-through mock echoing without contract assertions.
- **`[BE-TEST-05]` Bug-First Regression Lock**: Every PR fixing a bug ticket or with title `fix(...)` must introduce a test reproducing the defect prior to the fix.
## Structure
```
src/**/*.spec.ts # Unit tests (isolated logic)
test/**/*.e2e-spec.ts # E2E tests (full app flows)
```
## Unit Testing
- **Setup & Mocks (`[BE-TEST-04]`)**: Use `Test.createTestingModule()` with mocked providers. Ban 1:1 pass-through mock echoing.
- **Pattern & Cleanup**: AAA (Arrange-Act-Assert). Call `jest.clearAllMocks()` in `afterEach`.
- **Assertions (`[BE-TEST-03]`)**: Avoid shallow assertions like `expect(res).toBeDefined()`. Verify payload invariants.
- **Coverage**: Coverage is diagnostic and project-configured; verify risk-weighted critical paths rather than padding code for an arbitrary percentage.
## E2E Testing
- **Database (`[BE-TEST-02]`)**: Use real test DB (Docker). Never mock DB in E2E.
- **Cleanup**: Mandatory. Use transaction rollback or `TRUNCATE` in `afterEach`.
- **App Init**: Create app in `beforeAll`, close in `afterAll`.
- **Guards**: Override via `.overrideGuard(X).useValue({ canActivate: () => true })`.
## Strict TypeScript (MANDATORY)
- **No `any`**: Use typed objects, `jest.Mocked<T>`, or `as unknown as T`. Never `as any`.
- **No `eslint-disable`**: Fix underlying type issue. No exceptions.
- **Verify DTO shapes**: Read actual DTO class before writing mock data.
- **Cast Jest matchers**: Nested `expect.anything()` → `expect.anything() as unknown`.
- **No unused vars**: Only declare variables if referenced in assertions or setup.
## Anti-Patterns
- **`[BE-TEST-01]` Stylistic parameterized rewrites**: Do not demand `test.each` rewrites without a behavioral gap.
- **`[BE-TEST-02]` Brittle DB mock string matching**: Do not match SQL strings in mocks; use real DB.
- **`[BE-TEST-03]` Shallow assertions**: Ban shallow assertions like `expect(res).toBeDefined()`.
- **`[BE-TEST-04]` Pass-through mock echoing**: Ban 1:1 mock echoing without contract assertions.
- **`[BE-TEST-05]` Bug fix without reproduction test**: Ban bug fixes without a reproduction test.
- **No Private Tests**: Test via public methods, not service['privateMethod']. Never write tests for private methods solely to satisfy coverage targets.
- **No DB Mocks in E2E**: Use real DB with cleanup. Mocks defeat E2E purpose.
- **No Shared State**: Call `jest.clearAllMocks()` in `afterEach`. Random failures otherwise.
- **No Resource Leaks**: Always close app and DB in `afterAll`.
## References
Setup examples, mocking patterns, E2E flows, test builders, coverage config:
[references/patterns.md](references/patterns.md)
Strict-TypeScript patterns (Jest matchers, mock typing, DTO verification):
[references/strict-typescript-testing.md](references/strict-typescript-testing.md)
Pliki w paczce (5)
- SKILL.md 4 KB
- evals/evals.json 2 KB
- references/improve-coverage.md 2 KB
- references/patterns.md 6 KB
- references/strict-typescript-testing.md 6 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · HoangNguyen0403/agent-skills-standard | 100 | MIT |
| TheBushidoCollective/han | 91 | Apache-2.0 |
Migawka bazy z 28.10.2026 · wersja paczki 085a7e8bb2cd (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100nest-testing
Opisuje testowanie w NestJS: Test.createTestingModule, mockowanie providerów, testy e2e z supertest, mockowanie ORM i fixtury testowe. - 100typescript-e2e-testing
Prowadzi testy E2E i integracyjne projektów TypeScript i NestJS z Jest, supertest i prawdziwą infrastrukturą w Docker (Kafka, PostgreSQL, MongoDB, Redis) według wzorca Given-When-Then. - 100node-testing
Generuje testy jednostkowe i integracyjne HTTP dla API Node (Express, Fastify, Koa, NestJS) z Supertest na instancji aplikacji, z Vitest, Jest lub node:test. - 100typescript-unit-testing
Prowadzi testy jednostkowe projektów TypeScript i NestJS z Jest, @golevelup/ts-jest i bazami w pamięci według struktury AAA, w tym mockowanie i naprawę niestabilnych testów. - 100typescript-testing
Pisze testy TypeScript w Jest lub Vitest: testy jednostkowe i integracyjne, mocki oraz pokrycie kodu. - 95vitest-test-conventions
Podpowiada wzorce testów w Vitest dla NestJS: mocki, spy, it.each, testy endpointów przez supertest i fabryki.