code-to-tests

Automated test generation analyzes code's public interfaces at file and method levels to identify coverage gaps and create missing unit tests in the code/*/tests/ directory. It classifies coverage as covered, partial, or missing to target test generation accurately.

Analyzing method testability classifies methods as L1 untested or L2 undertested, while file coverage is categorized as covered, partial, or missing. This coverage analysis identifies exactly where unit tests are lacking across the codebase.

You run generated unit tests using the npm run test --workspaces command. The skill places new test files directly into the code/*/tests/ directory, allowing the workspace test runner to execute them seamlessly alongside existing tests.

Automated test generation supports refactoring by analyzing public interfaces and generating missing unit tests to improve coverage. Bringing new features or modified code up to a desired test coverage standard reduces manual effort and increases confidence in code changes.

Automated unit test generation analyzes existing test patterns alongside the code's public interface to create new test cases. Generated tests are placed directly into the code/*/tests/ directory to integrate with the current testing structure.