A specialist skill that designs and implements a testing strategy for a codebase. This skill should be used after code development and before code review.
Designs and implements comprehensive testing strategies after code development. Uses a checklist-driven workflow to analyze codebases, determine testing needs, and create unit, integration, and E2E tests with appropriate frameworks.
/plugin marketplace add nicholasgriffintn/claude-code/plugin install ng-workflow@claude-codeThis skill is limited to using the following tools:
This skill should only use read-only commands and avoid modifying files.
Copy this checklist and use it to track your progress through the testing strategy design process:
Testing Strategy Checklist
- [ ] Understand the Codebase
- [ ] Familiarize yourself with the codebase and its functionality.
- [ ] Identify recent changes made by developers.
- [ ] Determine Testing Needs
- [ ] Decide on the types of tests required (unit, integration, end-to-end, performance, security).
- [ ] Identify critical areas of the code that need thorough testing.
- [ ] Design Test Cases
- [ ] Create test cases that cover various scenarios, including edge cases and error handling.
- [ ] Ensure tests are clear, concise, and maintainable.
- [ ] Implement Tests
- [ ] Write the tests according to the designed test cases.
- [ ] Use appropriate testing frameworks and tools.
- [ ] Execute Tests
- [ ] Run the tests to validate the code changes.
- [ ] Analyze test results to identify any failures or issues.
- [ ] Maintain Tests
- [ ] Regularly update and maintain the test suite to ensure it remains relevant and effective.
When designing a testing strategy, consider the following pyramid structure to ensure a balanced approach:
/\
/ \ **E2E Tests** (10%)
/----\ - Critical user journeys
/ \ - Slow but comprehensive
/--------\ **Integration Tests** (20%)
/ \ - Component interactions
/------------\ - API contracts
/ \ **Unit Tests** (70%)
/________________\ - Fast, isolated
- Business logic focus
Choose appropriate testing frameworks based on the programming language and project requirements. Some popular options include:
JavaScript/TypeScript: For unit, use Vitest. For integration, use Vitest with MSQ. For E2E tests, use Playwright. For component tests, use Testing Library.
Python: For unit and integration tests, use Pytest. For E2E tests, use Playwright.
Ensure that your testing strategy covers the following aspects:
When designing tests, implement a mocking strategy to isolate components and simulate external dependencies. Consider the following guidelines:
Set minimum coverage thresholds to ensure adequate test coverage:
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.