write-tests

# Write Tests ## When to use Use this skill when code is untested, when a bug needs a regression test, or when coverage on a path is missing. ## Steps 1. Read the target and identify public behaviour, edge cases, and failure modes. 2. Choose the right level: unit for pure logic, integration for I/O and boundaries. 3. Write one test per behaviour using the project's existing framework and fixtures. 4. Include at least one edge case and one error-path assertion. 5. Run the suite and keep only tests that fail without the fix and pass with it. ## Examples - "Write pytest tests for utils/parser.py" - "Add integration tests for the /checkout endpoint" ## References Follow the project's test style; never test private internals or assert on exact error strings that may change.