diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-22 14:29:29 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-22 14:29:29 -0500 |
| commit | 6cc2a1d08a6a6ee10f9acee9b967f36827c0a27e (patch) | |
| tree | b2f327b1e25da22e6ea87ea309c9eb66932787a3 /pairwise-tests | |
| parent | 1825226035dfc7a1e567b0337281726837b607c5 (diff) | |
| download | rulesets-6cc2a1d08a6a6ee10f9acee9b967f36827c0a27e.tar.gz rulesets-6cc2a1d08a6a6ee10f9acee9b967f36827c0a27e.zip | |
docs(skills): add a category-exception protocol to add-tests
The Normal/Boundary/Error rule forced all three categories on every function, including pure adapters, generated code, and framework glue where a category would only re-test the framework. Step 7 now lets you skip a category in those cases, as long as you state and justify the skip in the plan and cover the behavior at integration or E2E level — a stated decision, never a silent omission. Step 12 points back to it.
The companion audit item about a missing typescript-testing.md reference turned out moot: that ruleset now exists and add-tests already references it correctly.
Diffstat (limited to 'pairwise-tests')
0 files changed, 0 insertions, 0 deletions
