test-generation

Purpose

Turn existing code into tests that would actually catch it breaking. The input is a function, class, module, or bug report; the output is test files in the project's own framework, in the right source set, that run and pass — plus a short statement of what is still untested.

The value is in case selection, not in typing. A test that only walks the happy path documents the code; it does not defend it. Most real defects live at the boundaries and in the error paths, so that is where the cases go.

When to use

• "Write tests for <file/function/class>" — new or existing code
• A bug was just fixed and needs a regression test that fails without the fix
• A module has no tests and needs a suite scaffolded
• Coverage is low and the question is what to test next, not how much