Test HTTP endpoints, CLIs, and library exports without internal calls.
npx skills add https://github.com/thrawn01/claude-dotfiles --skill surface-testing
Please help me install this Agent Skill. Skill: surface-testing Source: https://github.com/thrawn01/claude-dotfiles/tree/main/skills/surface-testing Command: npx skills add https://github.com/thrawn01/claude-dotfiles --skill surface-testing
Tests are written to exercise the system through its surface — HTTP endpoints, CLI entry points, and exported functions — while avoiding internal function calls. This approach preserves behavior across refactors and ensures users experience the system as intended.
Run surface tests against the application to verify public API behavior and end-user outcomes.
High-intent search queries and answers about installing and using this skill.
Surface testing validates system behavior by exercising end-user interfaces like HTTP endpoints, CLIs, and exported functions rather than internal components. This approach preserves test validity across refactors and ensures the system works as users actually experience it.
To test HTTP endpoints and CLIs without internal calls, you run tests strictly against the public surface. You validate observable outcomes from protocols and entry points, enforcing no direct calls to internal functions during the test run.
Yes, surface testing supports asynchronous behavior by emphasizing observability. When async work is in flight, the approach promotes surfacing important metrics to validate observable outcomes rather than relying on internal state checks.
Surface testing works across multiple surface types including HTTP, CLIs, and library exports. It ensures observable results across protocols by validating the behavior of exported functions as end-users interact with them.
You should switch to surface-level testing when you need confidence that refactors preserve behavior and end-user outcomes. Avoid internal testing when validating observable results across HTTP, CLI, or library surfaces is more critical than checking internal logic.
bdbchMap public interfaces of modules, packages, or systems.
heimeshoffEnforces red-green-refactor loops with executable acceptance-criteria tests before production code changes.
saranskumarPlans observability with logs, metrics, traces, and alerts for APIs and serverless components.
ivanshtokovGuide software teams through RED-GREEN-REFACTOR and AAA test cycles.
