Testing
Enterprise engineering workflow for Claude Code — not just prompts. AI agents that plan, build, audit, and ship with security gates, privacy checks, and approval-controlled commits. Safely adopt it into new or existing repositories.
npx -y skills add byerlikaya/claude-starter-kit --skill testingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 20 stars20 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
The how of testing: pyramid, AAA, isolation, risk coverage, determinism. Guarantees the DoD's "tests are green". test-expert-csk applies it. Trigger phrases: "write a test", "run the tests", "coverage", "are the tests green", "unit test", "integration test"
SKILL.md
1.4 KB, as published. Nobody here has run it
Testing Discipline
Goal: behavior correctness — test real behavior without breaking product code just to make a test pass.
Principles
- Pyramid: many unit, fewer integration, few end-to-end (e2e). Limit e2e to critical flows.
- AAA: Arrange-Act-Assert; one test = one behavior.
- Isolation & determinism: external dependencies are mocked/faked; time and randomness are fixed; test order is independent.
- Risk-coverage: risk, not metrics. Critical path + boundary + negative + authorization (IDOR/404) scenarios.
- Naming:
what_it_tests_under_which_condition_what_it_expects— on failure it is clear what broke. - Red-green: first a failing test, then the implementation.
Watch out
- Flaky = bug: an occasionally failing test is not tolerated; it is fixed at the root.
- In snapshot/golden-file tests, avoid needless brittleness (assert only the meaningful output).
DoD (this skill's contribution)
- The relevant test command is green (e.g.
dotnet test); critical paths are covered; no empty/meaningless tests.