httpx-test

Write tests for the current changes. Follow these steps:

1. Read CLAUDE.md to understand the project's test framework, conventions, and test commands.
2. Read any .claude/rules/*.md whose paths: glob matches the changed files — they capture testing conventions specific to this layer (e.g. how API tests are structured vs. how DB tests are structured).
3. Identify what changed with git diff master...HEAD (the whole branch's work), plus git diff and git diff --cached for any uncommitted edits — not a bare git diff, which would miss everything already committed on the branch. Classify the change:
   • Pure refactor (code moved/renamed, no behavior change): update existing tests' imports and call sites; do NOT invent new tests for behavior that already had coverage.
   • New behavior or modified behavior: continue to step 4.
4. Find existing test files for the modules you're testing. Read them fully — match their patterns:
   • File naming and location conventions.
   • Fixtures, factories, helpers, and setup/teardown patterns.
   • Assertion style and test structure.
   • How similar features are tested (use as a template).
5. Write focused tests that cover:
   • Happy path — the expected behavior works correctly.
   • Edge cases — empty inputs, boundary values, null/nil, large inputs.
   • Error cases — invalid input, missing data, permission failures. Test that errors are handled, not just that they don't crash.
   • Behavior, not implementation — test what the code does, not how it does it. Tests should survive a refactor that preserves behavior.
6. Run the test suite to verify everything passes, including your new tests.

Rules

• Match existing patterns. If the codebase uses factories, use factories. If it uses fixtures, use fixtures. Don't introduce a new testing pattern.
• Mock only: (1) external network services (HTTP APIs, payment gateways, third-party SDKs), (2) slow I/O without a fast fixture (real databases, filesystems), (3) non-deterministic sources (current time, randomness). Do NOT mock the code under test. Do NOT mock internal modules just to avoid setting them up.
• Don't under-test. If you changed a conditional, test both branches. If you added error handling, test the error path. "Happy path only" is not adequate coverage.
• Each test should test one thing. If a test name needs "and" in it, split it into two tests.
• Tests must be deterministic. No reliance on timing, ordering, or random data without seeds.
• A test that can't fail is worthless. For your key behavioral tests, make sure the assertion would actually break if the behavior were wrong — a green test against code you never verified can fail is false confidence. If a test passes no matter what, it's testing the mock or nothing.