sdcorejs-testing-philosophy

What problem does it solve?

Prevents weak or misleading test strategies by defining cross-track testing principles: test pyramid ratios, what to mock versus hit, when to write tests, and how to validate behavior instead of implementation.

Core Features & Use Cases

• Test pyramid guidance: recommends Unit/Integration/E2E ratios and what each layer must cover for speed vs confidence.
• Mocking vs hitting rules: clarifies which dependencies to mock (external services) and which to integrate (your owned DB/routers).
• When to write tests: supports TDD (before code), test-as-you-build (during), and diff-scoped tests (after) with anti-patterns to avoid.
• Arrange-Act-Assert structure and naming: enforces readable tests that express verified behavior and outcomes.
• Behaviour vs implementation: discourages brittle assertions on private methods and internal state shape.

Quick Start

Use the sdcorejs-testing-philosophy skill when planning tests for a new feature so the test plan matches the intended behaviour, layer, and mocking boundaries.