Testing Code

Unit tests verify individual functions and modules in isolation. Generate tests by specifying your code location and coverage target—the Skill creates test cases covering happy paths, edge cases, and error conditions to meet your coverage threshold, typically 80% or higher.

Unit tests verify single functions in isolation; integration tests verify module interactions and API contracts; end-to-end tests verify complete workflows. This Skill generates all three types, letting you test at each layer—from individual components to full system behavior—ensuring robust coverage across your codebase.

TDD writes tests before implementation, but you can retrofit it to legacy code. Provide your implementation and the Skill generates comprehensive tests—unit, integration, and edge-case—that document expected behavior and catch regressions, bringing existing code under TDD discipline.

Yes. The Skill identifies boundary conditions, invalid inputs, and error scenarios beyond typical use, then generates tests that verify your code handles them correctly. This prevents bugs in production and ensures error messages and recovery paths work as intended.

No. For integration tests across APIs or module interactions, the Skill provides scaffolding and mock examples so you can test component interactions without manual setup, reducing boilerplate and accelerating test suite buildout.

High test coverage—especially with edge cases—catches bugs early and gives confidence in refactoring and new features. This Skill generates maintainable, documentation-ready test patterns that serve as specifications, making coverage a metric for both safety and code clarity.