What problem does it solve? When teams are busy, test design steps get skipped because the reasoning behind each technique is unclear. This Skill consolidates the seven JSTQB/ISTQB testing principles and links each one to the specific techniques in the test-catalog, so you can justify why a technique is needed and decide which steps can safely be omitted. ## Core Features & Use Cases - Seven Principles Explained: Covers defect presence vs. absence, impossibility of exhaustive testing, early testing, defect clustering, the pesticide paradox, context dependence, and the zero-bug fallacy. - Technique Mapping: Each principle points to concrete techniques such as mutation testing, equivalence partitioning, boundary value analysis, risk-based testing, static review, exploratory testing, and acceptance testing. - Use Case: When deciding whether to skip mutation testing on a tight deadline, consult the pesticide paradox section to see that mutation testing exists precisely to verify your test suite still detects defects, then make an informed trade-off. ## Quick Start Ask the AI to explain which testing principle justifies using equivalence partitioning and risk-based test allocation for the current module.
