li3p/testmatch

Testmatch

Generate tests for: $ARGUMENTS

Workflow

1. Discover existing tests near the target and across the repository.
2. Read two or three representative test files before writing new tests.
3. Identify the local testing conventions:
   • framework and runner
   • assertion style
   • file naming and placement
   • fixtures, factories, setup, teardown, and cleanup
   • mocking and dependency injection style
   • async patterns and helper utilities
4. Read the target file completely.
5. Identify exported behavior, branches, error paths, and important invariants.
6. Write tests that look native to the project.

Test Requirements

Cover:

• happy paths
• error paths
• edge cases and boundary values
• nullish or empty inputs when relevant
• integration points that are likely to regress

Use only patterns already present in the repository unless the user explicitly asks to introduce a new testing approach.

Output

Create or update the test file in the location matching project convention. Summarize:

• tests added
• behavior covered
• any behavior that could not be tested cleanly
• the command the user should run to verify the tests