Create a test plan from a code diff

A useful plan follows the changed behavior and failure modes. It should explain what each test would prove rather than mirror implementation lines.

Use a reviewable project copy

Give the product or code teammate the relevant specification and a dedicated project folder or branch. Separate a proposed change from permission to release it. Request a diff or evidence table alongside the recommendation, and run checks that exercise the behavior in question. Generated code and test output still need review in the actual project environment.

Inputs for this workflow: A reviewed diff and the relevant behavior specification.

Work through the task

1. Identify changed inputs, state transitions and outputs.
2. Choose tests for boundaries and regressions.

A brief you can adapt

Draft test-plan.md with risk, scenario, expected behavior and test level. Separate existing coverage from proposed coverage.

The filenames above are examples. Replace them with your actual inputs and destination before submitting the task.

Review the deliverable

Ask whether a broken implementation would fail each proposed test.

Where this approach can fail

A generated plan does not establish coverage until the tests exist and have run.

For the related desktop setup, see local folder.