test

Final Test Pass

One pass, after development is done. No fixed process — only the result matters: changed behavior is covered and the suite passes.

Identify what changed in this session (git diff, files touched).
Detect the project's test framework and existing test layout; follow them exactly. If the project has no test setup, ask before introducing one.
Cover the changed public behavior: happy path plus the error and edge cases the change introduced. Skip trivial code (pure config, pass-through). Never assert on mock behavior; never add test-only methods to production code.
Run the relevant tests (the whole suite if it is cheap). Fix failures by root cause — a production bug fix beats a test adjustment.
Report: what is covered, what is deliberately not, and the passing test output.

One pass, after development is done. No fixed process — only the result matters: changed behavior is covered and the suite passes.

Identify what changed in this session (git diff, files touched).
Detect the project's test framework and existing test layout; follow them exactly. If the project has no test setup, ask before introducing one.
Cover the changed public behavior: happy path plus the error and edge cases the change introduced. Skip trivial code (pure config, pass-through). Never assert on mock behavior; never add test-only methods to production code.
Run the relevant tests (the whole suite if it is cheap). Fix failures by root cause — a production bug fix beats a test adjustment.
Report: what is covered, what is deliberately not, and the passing test output.