# Test Coverage Requirements

## Every module needs unit tests

If you add or modify a module, it must have a corresponding test file. No exceptions for "infrastructure" or "worker" code -- those break the hardest in E2E.

## Test the error paths

The happy path usually works. What breaks in E2E is:
- Malformed input (bad XML, raw source where markdown expected, missing config keys)
- Subprocess crashes (exit code != 0 with no output)
- Version mismatches (pytest 9 vs 8, different config section names)

Write tests for these cases, not just the golden path.
