본문으로 건너뛰기
cccskills
무료GitHub에 공개

nestjs-testing

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

실행 점수 미검증

설치 방법 보기

포함된 파일(5)

  • SKILL.md4.0 KB
  • evals/evals.json2.1 KB
  • references/improve-coverage.md2.4 KB
  • references/patterns.md6.5 KB
  • references/strict-typescript-testing.md6.2 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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

Strict-TypeScript patterns (Jest matchers, mock typing, DTO verification): references/strict-typescript-testing.md

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

HoangNguyen0403/agent-skills-standard5812026년 10월 24일 업데이트

Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their specific skills.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

HoangNguyen0403/agent-skills-standard5812026년 10월 24일 업데이트

Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

HoangNguyen0403/agent-skills-standard5812026년 10월 24일 업데이트

Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

HoangNguyen0403/agent-skills-standard5812026년 10월 24일 업데이트

Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

HoangNguyen0403/agent-skills-standard5812026년 10월 24일 업데이트

Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test recipes to their specific skills.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

HoangNguyen0403/agent-skills-standard5812026년 10월 24일 업데이트

HoangNguyen0403의 스킬 모두 보기

이 스킬의 문제 신고