typescript-e2e-testing
E2E and integration testing for TypeScript/NestJS projects using Jest, supertest, and real infrastructure via Docker (Kafka, PostgreSQL, MongoDB, Redis) with the Given-When-Then pattern. Use whenever the user is working on `.e2e-spec.ts` files or anything under `test/e2e/`, or asks to set up, write, review, run, debug, or optimize E2E or integration tests — including flaky tests, docker-compose for tests, Kafka/Redpanda consumers, test isolation, or GWT compliance.
Security Assessment
Detected risks:
About typescript-e2e-testing
The typescript-e2e-testing skill provides end-to-end and integration testing for TypeScript and NestJS projects using Jest and supertest against real infrastructure via Docker (Kafka, PostgreSQL, MongoDB, and Redis), following the Given-When-Then pattern. It activates for work on .e2e-spec.ts files or anything under test/e2e, and for setting up, writing, reviewing, running, debugging, or optimizing E2E and integration tests.
It is organized around six workflows (setup, writing, review, running, debugging, and optimize) selected by detecting the user's intent, each of which loads specific knowledge files. A structured references knowledge base covers shared fundamentals (core concepts, mandatory rules, best practices, GWT templates, NestJS setup, debugging) plus technology-specific folders for Kafka, PostgreSQL, MongoDB, Redis, and APIs with their rules, test helpers, Docker setups, and examples. A core principle is context efficiency: redirecting verbose E2E output to temp files with a unique session ID rather than the console, and fixing one failing test at a time.
It is most useful for engineers building or maintaining E2E and integration tests for NestJS services that depend on real infrastructure, including handling flaky tests, test isolation, and performance optimization.
FAQ
When should I use this skill?
When working on .e2e-spec.ts files or test/e2e, or asking to set up, write, review, run, debug, or optimize E2E and integration tests for TypeScript/NestJS.
What stack does it target?
TypeScript and NestJS with Jest and supertest, running against real Kafka, PostgreSQL, MongoDB, and Redis infrastructure via Docker, using the Given-When-Then pattern.
How is it organized?
Around six intent-selected workflows (setup, writing, review, running, debugging, optimize), each loading specific reference knowledge files for the relevant technology.
How does it keep output manageable?
By redirecting verbose E2E test output to temp files with a unique session ID instead of the console, to avoid bloating agent context.
Does it help with flaky tests?
Yes. It covers test isolation (for example Kafka pre-subscription patterns), debugging one failing test at a time, and performance optimization.
All Files
103 filesInstall typescript-e2e-testing
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
bmad-labs/skills