AgriciDaniel/claude-code-essentials-vs-code / templates/skills/testing
testing
UnverifiedWrite comprehensive tests
When writing tests:
- Use descriptive names: "should [behavior] when [condition]"
- Follow Arrange-Act-Assert (AAA) pattern
- Test edge cases: null, empty, boundary values
- Mock external dependencies appropriately
- Prefer integration tests for critical paths
- Aim for 80% coverage minimum
- Use test fixtures for complex data setup
- Test error scenarios and edge cases
- Keep tests independent and isolated
- Use parameterized tests for similar scenarios
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |