code-testing

Plan, write, and maintain software tests through public interfaces.

7|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/nweii/agent-stuff --skill code-testing-nweii
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-testing
Source: https://github.com/nweii/agent-stuff/tree/main/skills/code-testing
Command: npx skills add https://github.com/nweii/agent-stuff --skill code-testing-nweii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code Testing helps teams plan, write, review, and maintain software tests, reducing regression risk by focusing on behavior over implementation.

Core Features & Use Cases

  • Test-first loop: Start with planning interfaces, write a tracer bullet test, then implement minimally to green.
  • Desiderata-guided reviews: Use Kent Beck's properties to assess tests for isolation, determinism, readability.
  • Strategic testing decisions: Decide appropriate test level (unit, integration, e2e) depending on risk and context.
  • This skill emphasizes testing the public interface and guidelines around mocking and interface design.
  • Use cases include feature development, bug fixes, code reviews, and auditing test suites.

Quick Start

Begin a test-first loop by planning the interface, writing a tracer bullet test, and implementing only enough code to pass.

Frequently Asked Questions about code-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write unit tests that verify behavior without testing implementation details?

Use a test-first loop: plan interfaces, write a tracer bullet test, then implement minimally to green. This approach enforces testing public interfaces to ensure behavior verification without coupling tests to internal implementation details.

What is the best way to decide between unit, integration, and e2e testing?

Evaluate risk and context to choose the appropriate test level. This skill guides strategic testing decisions across unit, integration, and e2e testing, ensuring the selected method matches the regression risk and behavioral complexity of the target code.

How do I apply TDD to feature development and bug fixes?

Start with a test-first loop: plan the interface, write a tracer bullet test, then implement minimally to green. This incremental workflow applies directly to feature development and bug fixes, ensuring behavior is verified through public interfaces.

What are Kent Beck's desiderata for reviewing and maintaining software tests?

Desiderata-guided reviews use Kent Beck's properties to assess tests for isolation, determinism, and readability. This skill applies these properties during code reviews and test suite audits to maintain high-quality, reliable tests over time.

When should I use mocking in integration and e2e testing?

Use mocking based on interface design guidelines that prioritize testing public interfaces. This skill provides principled mocking guidelines to ensure integration and e2e tests remain isolated, deterministic, and focused on behavior verification.