Do I need to install specific tools for Level 1 tests?

Level 1 tests rely only on standard developer environment tools like Node.js, npm, git, and Unix shell utilities, ensuring they are fast and portable.

Why does this skill discourage mocking?

Mocking is often a sign of poor code design and tests implementation details rather than outcomes. This skill promotes dependency injection to create more resilient, reality-based tests.

When should I move from Unit to Integration tests?

Escalate to Level 2 (Integration) only when you need to verify that your code works correctly with real local binaries or project-specific tools that Level 1 cannot simulate.

What is the 'Progress vs Regression' test rule?

Progress tests live in the specs folder and can be 'Red' during development. Regression tests in the 'test/' directory must always be 'Green' to ensure the code is always deployable.

TypeScript Testing Methodology

Name: TypeScript Testing Methodology
Author: simonheimlicher

bysimonheimlicher

•

보안 및 테스팅

Implements a high-confidence, three-tiered testing framework for TypeScript using dependency injection and behavior-driven patterns.

소개

This skill provides a structured methodology for testing TypeScript applications across three specific levels: Unit (Level 1), Integration (Level 2), and E2E (Level 3). It moves away from fragile mocking frameworks in favor of dependency injection and 'Reality as the Oracle,' ensuring tests verify what the system does rather than how it is implemented. By segregating 'Progress tests' for TDD from 'Regression tests' for CI stability, it allows developers to maintain a green deployment gate while iterating rapidly on new features.

주요 기능

Dependency injection patterns to eliminate fragile module mocking
Segregated Progress vs. Regression test workflow for CI stability
1 GitHub stars
Three-tiered testing architecture (Unit, Integration, E2E)
Standardized Vitest configuration and type-safe test factories
Behavior-focused verification strategies

사용 사례

Implementing TDD for new TypeScript features without breaking CI pipelines
Graduating unit tests into full-scale E2E workflows as feature confidence grows
Refactoring legacy TypeScript code by replacing mocks with real dependencies

소개

주요 기능

Dependency injection patterns to eliminate fragile module mocking
Segregated Progress vs. Regression test workflow for CI stability
1 GitHub stars
Three-tiered testing architecture (Unit, Integration, E2E)
Standardized Vitest configuration and type-safe test factories
Behavior-focused verification strategies

사용 사례

Implementing TDD for new TypeScript features without breaking CI pipelines
Graduating unit tests into full-scale E2E workflows as feature confidence grows
Refactoring legacy TypeScript code by replacing mocks with real dependencies