Testing Strategist
CheckedGenerates comprehensive test plans, including edge cases and data variations, to maximize software quality coverage.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
Testing Strategist, not the name it is listed under, so the command below uses that name.- 1
Run this in your project
terminal$ npx skills add daffy0208/ai-dev-standards --skill "Testing Strategist" -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
daffy0208
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned daffy0208/ai-dev-standards at 32c3241e48.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 32c3241e48
- Scanned
- 3 files, 1,208 lines
About this skill
What it does
The Testing Strategist skill helps AI agents generate comprehensive test plans, focusing on maximizing software quality coverage while adhering to the principles of the testing pyramid. It emphasizes creating tests that are fast, isolated, repeatable, self-checking, and timely, aligning with best practices for efficient and reliable software development. The skill prioritizes unit tests (70%), followed by integration tests (20%) and end-to-end (E2E) tests (10%).
When to use it
- Generating Unit Tests: When you need help creating isolated tests for individual functions, components, or classes.
- Structuring Test Plans: To ensure a balanced testing approach aligned with the 70/20/10 unit/integration/E2E test ratio.
- Identifying Test Candidates: When seeking guidance on what aspects of your code (e.g., business logic functions, React components) are good candidates for testing.
- Creating tests alongside new code: To promote a "Test-Driven Development" (TDD) approach.
Key capabilities
- Testing Pyramid Guidance: Provides recommendations based on the 70/20/10 unit/integration/E2E test ratio.
- Unit Test Focus: Specializes in generating tests for individual functions, components and classes.
- Test Quality Principles: Encourages tests that are fast, isolated, repeatable, self-checking, and timely.
- Candidate Identification: Suggests suitable code sections for unit testing (e.g., business logic, utility functions).
Example prompts
- "Generate unit tests for this
calculateTotalfunction: [code snippet]" - "What are good candidates for unit tests in my React component?"
- "Create a test plan following the testing pyramid principles for a new feature."
Tips & gotchas
- The skill primarily focuses on generating unit tests. It does not directly create integration or E2E tests.
- It assumes third-party libraries and framework internals are already tested and should be skipped when creating unit tests.
- To get the most out of it, provide clear code snippets for which you need test generation assistance.