Decide whether a change warrants new tests and choose proportionate verification. Use before adding tests, when planning validation, or when reviewing whether a proposed test protects meaningful behavior.
Scanned 8/31/2026
Install to Claude Code
Skills Directorynpx -y skills add FranciscoMoretti/chat-js --skill strategic-testing --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Strategic Testing?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/franciscomoretti-strategic-testing)More formats (shields.io, HTML) on the badges page.
---
name: strategic-testing
description: Decide whether a change warrants new tests and choose proportionate verification. Use before adding tests, when planning validation, or when reviewing whether a proposed test protects meaningful behavior.
---
# Strategic testing
Add tests only when they protect meaningful behavior or a stable contract that
existing checks could realistically miss.
- Prioritize domain invariants, important edge cases, public interfaces,
persisted data, security boundaries, and integration seams.
- Skip tests for mechanical edits, implementation details, existing coverage,
or changes already verified by types, linting, or schema validation.
- Choose the smallest test level that protects the behavior.
Before adding a test, identify the realistic failure it prevents and confirm
that the maintenance cost is justified. If that case is weak, do not add one.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
