testing-patterns

Standardizing test pyramid proportions involves defining distinct roles for unit, integration, and end-to-end tests. This skill provides structured guidance and recommended proportions to balance your test suite, ensuring reliable coverage without excessive E2E overhead.

The TDD workflow for new features mandates a test-first approach. This skill provides structure for writing failing tests, implementing passing tests, and refactoring, ensuring quality assurance is built into the development cycle from the start.

Avoiding over-mocking requires recognizing anti-patterns like testing mocks or leaving incomplete mocks. This skill highlights these common traps and provides practical remedies and gate rules to ensure your mocking strategies maintain test quality.

Yes, you can use this to define test coverage targets and code review checklists. It outlines specific coverage goals, naming conventions, and review standards that teams can apply directly to evaluate test quality during feature reviews.

You need standardized testing patterns when ambiguity slows down development and onboarding. This skill reduces ambiguity in how tests are written and reviewed, accelerating onboarding for new developers and ensuring consistent quality assurance across projects.