What problem does it solve? Teams often focus only on functional correctness and miss defects that live outside it: where to insert tests in the delivery pipeline, how to catch bugs without executing code, and how to verify idempotency, concurrency, and boundary behavior. This Skill provides structured procedures and completion checklists for those process, static, and miscellaneous testing concerns. ## Core Features & Use Cases - Process test tactics (Group B): Covers BDD/Gherkin, ATDD, CI automation, shift-left/shift-right, canary and blue-green releases, feature flags, synthetic monitoring, mutation/coverage CI gates, test data management, and flaky test handling, with a TypeScript cucumber-js example. - Static testing (Group C): Step-by-step procedure for selecting linter/type-checker rule sets, applying them to all files, driving violations to zero, and enforcing them via CI gates, plus code review and complexity metrics guidance. - Idempotency, concurrency, and boundary testing (Group D): Concrete start-to-finish procedures with completion checklists for idempotency tests, race condition tests, and negative/boundary-value tests derived from equivalence partitioning. - Use Case: When the test-catalog router assigns a technique like idempotency testing or static analysis to a behavior, open this Skill to get the execution procedure, a minimal TypeScript example, and a checklist confirming nothing was missed. ## Quick Start Ask the AI to apply the idempotency testing procedure from this Skill to your retry-prone operations and verify each one against the completion checklist.
