Write Tests

What to generate

Cover these cases in order of priority:

1. Happy path — expected inputs produce expected outputs
2. Edge cases — null/undefined/empty, boundary values, zero, empty collections
3. Error cases — invalid inputs, thrown exceptions, rejected promises
4. Integration points — if the code calls external services or the database, write tests with appropriate mocks/stubs matching the project's style

Do not generate tests for private/internal helpers unless they are the explicit target.

Output

Write the test file to the location that matches the project's convention (co-located, __tests__/, tests/, etc.).

After writing, print:

• The file path written
• A bullet list of what each test group covers
• Any assumptions made (e.g. "assumed Jest based on package.json")
• Any cases that could not be tested without additional context

Gotchas

• Match the existing style exactly — do not introduce a new framework or assertion style.
• Do not add tests that only verify implementation details (testing private state, exact call counts for internal calls).
• If the target has no existing tests, note this but still write tests based on the code's behaviour.
• If the code is untestable as-is (e.g. tight coupling, no dependency injection), note what refactoring would enable testing rather than writing poor tests.