testland/input-domain-coverage-audit
Audits a test file's input-domain coverage per entry point across three axes: equivalence partitioning (clustering the literal values the tests actually pass, to infer which partitions are exercised), boundary value analysis (recorded n/a when the entry point declares no bound), and error/negative-path coverage (classifying every matcher as positive or negative and computing the negative-assertion ratio). Emits a PASS / SHALLOW / N/A verdict per axis per entry point, with the evidence that produced it. Owns whether the test data spans the input space, not whether an individual assertion is specific enough: matcher specificity belongs to `test-code-conventions`. Use when a test file's cases all look alike - every argument the same shape, every response a success, no thrown-error case - and the suite needs a defensible answer on whether it exercises more than one equivalence class before it is approved.
70
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
grounding.mdreferences/
Grounding - verbatim source quotations
The SKILL.md spine cites these sections with one-line summaries. The full quotations are kept here.
§EP - equivalence partitioning (CTFL v4.0.1 §4.2.1, page 39)
Source: ISTQB Certified Tester Foundation Level syllabus v4.0.1 (PDF).
The coverage criterion: "In EP, the coverage items are the equivalence partitions. To achieve 100% coverage with this test technique, test cases must exercise all identified partitions (including invalid partitions) by covering each partition at least once."
Each Choice coverage, for entry points with several parameters: "requires test cases to exercise each partition from each set of partitions at least once", and it "does not take into account combinations of partitions".
The coverage formula: partitions exercised by at least one test case, divided by total partitions identified, expressed as a percentage. Coverage is "the degree to which specified coverage items are exercised by a test suite, expressed as a percentage".
§BVA - boundary value analysis (CTFL v4.0.1 §4.2.2, page 40)
The scope rule: BVA "is a test technique based on exercising the boundaries of equivalence partitions. Therefore, BVA can only be used for ordered partitions."
2-value BVA: "In 2-value BVA, for each boundary value there are two coverage items: this boundary value and its closest neighbor belonging to the adjacent partition. To achieve 100% coverage with 2-value BVA, test cases must exercise all coverage items."
3-value BVA, the stricter bar: "for each boundary value there are three coverage
items: this boundary value and both its neighbors", which adds min+1 and
max-1 to the required set.
§NEG - AI test-generation survey stat
An industry survey found 70% of teams use AI for test-case creation but only 19.9% for risk identification, with 40.7% of adopters citing "more diverse and complex test cases" as a benefit (PractiTest State of Testing). Generating more cases is not the same as widening the input domain.