claudeskills.page

Collection · 12 skills

Testing & Quality

Layer the testing pyramid properly: small fast unit tests written test-first, contract and API tests at the boundaries, a thin set of end-to-end flows, fuzzing and load tests where risk lives, and a process for killing flaky tests instead of retrying them.

Best for Engineers and QA leads raising confidence in every merge.

What's inside

Listed in the order we suggest adopting them. You don't call them by name: each skill loads on its own when a request matches it.

  1. TDD Loop See it fail, make it pass, then clean it up Engineering Workflow tdd-loop 192 lines
  2. Unit Testing Tests that survive refactors and catch real bugs Testing unit-testing 188 lines
  3. Mocking Strategy Mock the edges, run everything you own Testing mocking-strategy 161 lines
  4. API Testing Prove every endpoint's contract, including who can't call it Testing api-testing 254 lines
  5. Contract Testing Catch breaking API changes before either side deploys Testing contract-testing 182 lines
  6. Playwright E2E End-to-end tests that never need a sleep Testing playwright-e2e 220 lines
  7. Fuzz Testing Throw hostile bytes at parsers before attackers do Testing fuzz-testing 259 lines
  8. Load Testing with k6 A verdict and a bottleneck, not just a pile of numbers Testing load-testing 190 lines
  9. Coverage Analysis Find untested risk instead of chasing a percentage Testing coverage-analysis 189 lines
  10. Flaky Test Triage Find flakes from CI data and fix the cause Testing flaky-test-triage 149 lines
  11. Testcontainers Real databases in tests, started once and reset fast Testing testcontainers 202 lines
  12. Benchmark Testing Faster means significant, not one lucky run Testing benchmark-testing 259 lines

Keep exploring

Other collections

All collections →
esc