axiomantic/testing-strategy
skills/testing-strategy/SKILL.md
Test selection strategy and scope guidance. Triggers: 'which tests should I run', 'test tiers', 'test marks', 'slow tests', 'integration vs unit', 'cross-module regression', 'test scope', 'what should I run', 'select tests', 'test batching'. NOT for: writing tests (use test-driven-development) or fixing broken tests (use fixing-tests).
$ install --global
skillsauthnpx skillsauth add axiomantic/spellbook testing-strategyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 3, 2026, 3:22 PM70.9s1 file scanned
SKILL.md
- name:
- testing-strategy
- description:
- Test selection strategy and scope guidance. Triggers: 'which tests should I run', 'test tiers', 'test marks', 'slow tests', 'integration vs unit', 'cross-module regression', 'test scope', 'what should I run', 'select tests', 'test batching'. NOT for: writing tests (use test-driven-development) or fixing broken tests (use fixing-tests).
- intro:
- |
<analysis>
Reference for choosing which tests to run based on change scope, and diagnosing cross-module regressions when targeted tests pass but the full suite fails.
</analysis>
<reflection>
Did I match test scope to change scope, and did I avoid running the full suite when targeted tests would suffice?
</reflection>
Testing Strategy
Invariant Principles
- Scope Matches Change - Test selection mirrors the scope of the code change; a single-file change does not justify a full suite run.
- Marks Are Proactive - Tests are marked (slow, gpu, network) at authoring time based on what they require, not how fast they happen to run today.
- Full Suite Runs Once - The complete test suite runs once per work unit completion, not after every incremental change.
Test Tiers
| Tier | Time | What | When | |------|------|------|------| | Unit | <1s each | Pure logic, no I/O, no external deps | After every change | | Integration | 1-5s each | Real resources (DB, filesystem, network) | After completing a logical unit of work | | E2E / Slow | >5s each | Full pipelines, large data, real services | Once per feature branch, before PR |
Selecting What to Run
- Single file changed: Run only the test file(s) that directly test that module.
src/auth/login.pychanged? Runtests/test_login.py. - Shared dependency changed (types, config, utilities): Grep for imports of the changed module across test files. Run all direct consumers.
- Multi-file task complete: Run unit tests for all changed files in one command.
- All tasks in a work unit complete: Run the full suite once.
- If >5 test files affected: Run the full fast tier rather than listing individually.
Batching: Write code for task 1, run targeted tests, write code for task 2, run targeted tests, run full suite once at end.
Writing Tests for Speed
Mock expensive resources in unit tests. Use smallest possible inputs. Never sleep in tests. One assertion focus per test. No fixtures heavier than the test itself.
Test Marks
Apply marks proactively when writing tests. A test that calls a GPU kernel is a GPU test even if it is fast today.
| Mark | Meaning |
|------|---------|
| slow | >5 seconds. Skip during rapid iteration. |
| gpu, hardware | Requires specific hardware. Skip on machines without it. |
| network / external | Calls external services. Skip in offline/fast modes. |
| integration | Requires multiple components working together. |
| smoke | Minimal sanity checks. Run first. |
If a project lacks marks, infer tiers from --durations=0 (pytest) or equivalent: >5s is slow, >1s is integration, the rest are unit.
Cross-Module Regression
When the full suite fails after targeted tests passed: check failed test imports against your changed modules, then investigate shared mutable state, test ordering, or resource contention.
Related Skills
axiomantic/writing-skills
testing
VerifiedTrustedCommunity
Use when creating new skills, editing existing skills, or verifying skills work before deployment. Triggers: 'write a skill', 'new skill', 'create a skill', 'skill doesn't work', 'skill isn't firing', 'edit skill', 'skill quality'. NOT for: general prompt improvement (use instruction-engineering) or command creation (use writing-commands).
5SKILL.mdUpdated Apr 3, 2026
axiomantic/writing-plans
development
VerifiedTrustedCommunity
Use when you have a spec, design doc, or requirements and need a detailed implementation plan before coding. Triggers: 'write a plan', 'create implementation plan', 'plan this out', 'break this down into steps', 'convert design to tasks', 'implementation order'. Also invoked by develop during planning. NOT for: reviewing existing plans (use reviewing-impl-plans).
5SKILL.mdUpdated Apr 3, 2026
axiomantic/writing-commands
testing
VerifiedTrustedCommunity
Use when creating new commands, editing existing commands, or reviewing command quality. Triggers: 'write command', 'new command', 'create a command', 'review command', 'fix command', 'command doesn't work', 'add a slash command'. NOT for: skill creation (use writing-skills).
5SKILL.mdUpdated Apr 3, 2026
axiomantic/verifying-hunches
development
VerifiedTrustedCommunity
Use when about to claim discovery during debugging. Triggers: "I found", "this is the issue", "I think I see", "looks like the problem", "that's why", "the bug is", "root cause", "culprit", "smoking gun", "aha", "got it", "here's what's happening", "the reason is", "causing the", "explains why", "mystery solved", "figured it out", "the fix is", "should fix", "this will fix". Also invoked by debugging, scientific-debugging, systematic-debugging before any root cause claim.
5SKILL.mdUpdated Apr 3, 2026