Skip to content

AgriciDaniel/claude-code-essentials-vs-code / templates/skills/testing

testing

Unverified

Write comprehensive tests

When writing tests:

  1. Use descriptive names: "should [behavior] when [condition]"
  2. Follow Arrange-Act-Assert (AAA) pattern
  3. Test edge cases: null, empty, boundary values
  4. Mock external dependencies appropriately
  5. Prefer integration tests for critical paths
  6. Aim for 80% coverage minimum
  7. Use test fixtures for complex data setup
  8. Test error scenarios and edge cases
  9. Keep tests independent and isolated
  10. Use parameterized tests for similar scenarios
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 318kUpdated Claude CodeCodexUnverifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 318kUpdated Claude CodeCodexUnverifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 318kUpdated Claude CodeCodexUnverifiedInstall
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: 196kUpdated Claude CodeCodexVerifiedInstall