test-scaffolder

You can scaffold unit and e2e tests by running a Python script that generates per-submodule unit test stubs, end-to-end test skeletons, and integration glue to validate cross-module wiring. This requires a documented module and sub-module plan.

Red-phase test scaffolding generates actionable, failing test stubs aligned to project documentation. It provides traceable test IDs mapped to sub-modules, ensuring complete coverage before implementation begins in a multi-module project.

Yes, you need Python 3.x and a scripts directory to run the test generation script. The scaffolder uses these to map deterministic test IDs to your documented sub-module plan and output pytest-compatible stubs.

Yes, the scaffolder generates an integration test layer that validates inter-module wiring. When you provide an N sub-modules blueprint, it creates the integration path tests alongside the individual unit and end-to-end test stubs.

Provide a documented module and sub-module plan to map IDs to tests, then execute the scaffold script with the module name and comma-separated sub-modules. This generates standardized, deterministic unit and e2e test skeletons for each component.

Test scaffolding requires a documented module plan because the generator maps deterministic test IDs directly to your sub-module blueprint. Without this documented plan, the tool cannot create traceable stubs or wire the cross-module integration tests.