gen-tests

Generating test stubs from project specs is done by reading the specs directory and mapping documented behavior to unit, integration, and end-to-end test placeholders. This process creates a structured coverage backlog without overwriting existing tests.

You can create a coverage backlog without overwriting existing tests because the system detects the active test runner and writes stubs using project conventions. It records what already exists and only adds new placeholders for missing coverage.

Spec-to-test planning works by reading documented flows, endpoints, and invariants from the specs directory, then mapping them directly to organized test stubs. This converts documented behavior into a planned coverage backlog.

This test generation approach supports unit, integration, and end-to-end testing by detecting the active test framework in the project. It then generates framework-aware stubs that align with the established testing conventions.

A stub inventory is an index that records what test stubs were created, what already exists, and whether each stub is an active todo or inactive planning placeholder. It provides a structured backlog to manage coverage gaps systematically.

You should avoid automated test stub generation if your project lacks documented specs, as the tool relies on reading a specs directory to map flows and invariants. Without existing specs, there is no source material to generate the coverage backlog.