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.
- 0
- Installs
- —
- Rating
- —
- Success rate
- 5
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 53dbd43f7346a412… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
SKILL.md
NestJS Testing
Priority: P2 (MEDIUM)
Core Rule Anchors
[BE-TEST-01]Parameterized Tests for Equivalent Cases: Prefertest.eachwhen 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 onlyexpect(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 titlefix(...)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]): UseTest.createTestingModule()with mocked providers. Ban 1:1 pass-through mock echoing. - Pattern & Cleanup: AAA (Arrange-Act-Assert). Call
jest.clearAllMocks()inafterEach. - Assertions (
[BE-TEST-03]): Avoid shallow assertions likeexpect(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
TRUNCATEinafterEach. - App Init: Create app in
beforeAll, close inafterAll. - Guards: Override via
.overrideGuard(X).useValue({ canActivate: () => true }).
Strict TypeScript (MANDATORY)
- No
any: Use typed objects,jest.Mocked<T>, oras unknown as T. Neveras 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 demandtest.eachrewrites 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 likeexpect(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()inafterEach. 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
Files
5- SKILL.md
d29bb512864.0 KB - evals/evals.json
2a56f2c2d02.1 KB - references/improve-coverage.md
df137064102.4 KB - references/patterns.md
8ca2650d606.5 KB - references/strict-typescript-testing.md
3ccfd19ac36.2 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from HoangNguyen0403/agent-skills-standard8
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.
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 spec
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.
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.
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.
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 reci
Configure release signing, R8 obfuscation, and App Bundle publishing for Android. Use when setting up signing configs, enabling minification, adding ProGuard keep rules, or preparing for Play Store submission.
Enforce Material Design 3 theming and design token usage in Jetpack Compose. Use when implementing M3 components, color schemes, typography, or design tokens.
Related backend skillsscan passed
PostHog integration for server-side Node.js applications using posthog-node
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs. Use when designing or reviewing REST endpoints, resource names, status codes, pagination, or versioning.
Report browser/API/CLI/job/worker/webhook bugs. (gstack)
This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT} with MCP", or discusses MCP server types (SSE, stdio, HTTP, WebSocket). Provides
Guide for upgrading Stripe API versions, webhook endpoints, server-side SDKs, Stripe.js, and mobile SDKs
Create and compose tRPC middleware with t.procedure.use(), extend context via opts.next({ ctx }), build reusable middleware with .concat() and .unstable_pipe(), define base procedures like publicProcedure and authedProcedure. Access raw input with getRawInput(). Logging, timing, OTEL tracing pattern