NestJS E2E Practices

Build E2E suites that prove the delivered NestJS system through its public HTTP boundary. Load only the cards needed for the current decision; the cards own detailed rules, examples, exceptions, and sources.

When to Apply

• Create, extend, review, or repair NestJS HTTP E2E tests.
• Design Jest discovery, a main orchestrator, feature orchestrators, shared context, or teardown.
• Configure a production-like NestJS test application and isolated database lifecycle.
• Create fixtures, validation cases, authentication flows, and public contract assertions.
• Isolate an external email, payment, SMS, webhook, or similar out-of-process dependency.

Do not apply this skill to unit tests, repository-only integration tests, black-box tests against deployed APIs without NestJS source access, non-NestJS APIs, or browser-only UI testing.

Rule Categories by Priority