Test Gen

Detect the project's test framework by checking config files and existing tests:

If no config file is found, check existing test files and match their patterns.

3. Generate Tests

For each function/method, generate tests covering:

Happy Path

• Normal inputs with expected outputs
• Common use cases

Edge Cases

• Empty inputs (null, undefined, empty string, empty array)
• Boundary values (0, -1, MAX_INT, empty collections)
• Type edge cases (NaN, Infinity for numbers)

Error Cases

• Invalid inputs that should throw/return errors
• Missing required parameters
• Malformed data

Integration Points (if applicable)

• Mock external dependencies
• Verify correct calls to dependencies
• Test error propagation from dependencies

4. Output

Write test files following project conventions:

• Location: Adjacent to source (e.g., utils.test.ts) or in tests/ directory — match existing pattern
• Naming: Match project convention (*.test.*, *_test.*, test_*.*)
• Style: Match existing test style (describe/it, test(), t.Run, etc.)

Test Quality Rules

• Each test should test ONE behavior
• Test names should describe the expected behavior, not the implementation
• Use descriptive assertion messages
• Avoid testing implementation details — test behavior and contracts
• Keep tests independent — no shared mutable state
• Prefer real values over mocks when practical
• Include setup/teardown only when necessary