testing-philosophy

What problem does it solve?

Poorly written tests (testing implementation, too many mocks, brittle assertions) provide false confidence and slow down development. This Skill provides universal principles for writing effective, maintainable tests that truly verify behavior.

Core Features & Use Cases

• Behavior Over Implementation: Guides you to test what code does, not how it does it, ensuring tests remain stable during refactoring.
• Minimize Mocks & AAA Structure: Promotes using real objects when possible and structuring tests clearly with Arrange, Act, Assert phases.
• Meaningful Coverage: Focuses on testing critical paths and edge cases for confidence, rather than chasing arbitrary percentage targets.
• Use Case: When writing new tests, activate this Skill to automatically review your test structure, mock usage, and assertions, ensuring they adhere to best practices and provide maximum value.

Quick Start

Apply the testing-philosophy skill to review the attached unit test. Suggest improvements for its structure and mocking strategy.