principle-testing

What problem does it solve?

This Skill helps you build and evaluate a test strategy that produces trustworthy confidence instead of misleading coverage numbers.

Core Features & Use Cases

• Test pyramid strategy: choose the right balance of unit, integration, and e2e tests to avoid brittle suites and slow feedback loops.
• Test doubles taxonomy: select stubs, fakes, spies, and mocks with clear rules for when mocking is appropriate (trust boundaries only).
• Confidence measurement: use coverage intelligently and apply mutation testing to detect weak assertions and gaps.
• Flaky test triage: diagnose common root causes like shared state, timing/order dependence, and undeclared external dependencies.
• Contract testing: verify consumer/provider expectations (including async/message-based contracts) to catch integration drift earlier.
• Test data & properties: use builders/fixtures for readability and apply property-based and characterization tests for robustness and safe refactors.

Quick Start

Ask for guidance on how to structure my unit/integration/e2e mix for a specific system and how to decide between real dependencies, fakes, and mocks.