Testing Patterns

**Judgement:** This is a high-quality, broadly applicable reference for software testing patterns. It is well-suited as a default assistant skill whenever users ask for tests, testing strategy, or test improvements. **Strengths:** - Encourages solid, widely accepted practices (AAA, test pyramid, DI, mocking at boundaries). - Provides multi-language examples and concrete code snippets for common frameworks. - Covers quality criteria, coverage strategy, test organization, and clear anti-patterns. **Risks / Limitations:** - Assumes a relatively standard web/service architecture; less tailored to highly specialized domains (embedded, real-time, hard‑RT systems). - Opinionated emphasis on the classic testing pyramid may not match teams that intentionally favor heavy E2E or contract testing. - Does not itself inspect or execute code, so it must be paired with code-understanding skills for context-specific correctness. **Recommended Scenarios:** - Use as a backbone for any request like “write tests”, “add test coverage”, “fix flaky tests”, or “design a testing strategy”. - Combine with code-aware tools when generating or refactoring concrete test suites in specific repositories. - Use to enforce consistent testing style and avoid common testing anti-patterns in code review or CI assistant workflows.