Test Map

Test Map

Use this page after Where to Change Code to choose the smallest validation that covers a change, then expand outward only when needed.

Prefer just recipes on Windows

On Windows, prefer project just recipes when a local proxy may be running. They avoid target-directory conflicts with a locked target/debug/proxai.exe.

Validation by change type

Change area	Start with	Then consider
Docs only	just site check	Manual navigation for new IA or component-heavy pages
Formatting only	cargo fmt --check	just check before merging broader edits
Config schema/defaults	Focused config loading tests	pixi run cargo test --lib or just check
Route matching	Route matching unit/e2e tests	just test-e2e if proxy behavior changes
Protocol conversion	Pair-specific conversion tests	Proxy e2e tests for request/response behavior
Streaming/SSE/tool calls	Targeted streaming tests and fixtures	just test-e2e because streaming regressions are user-visible
Error rendering	Error projection tests	HTTP and SSE error behavior checks when stream state matters
Capture/logging	Capture behavior tests and docs checker phase coverage	Privacy review of generated artifacts

Test selection workflow

1. 1

   Identify the boundary

   Goal: Avoid running broad tests before you know what changed.

   Do

   • Map the change to config, routing, translation, streaming, errors, capture, docs, or release packaging.
   • Use source ownership from developer/where-to-change-code.

   Verify: You can name the primary module and user-visible behavior affected.

   Where to Change Code
2. 2

   Run the narrowest meaningful check

   Goal: Catch local mistakes quickly.

   Do

   • Use docs checks for docs-only changes.
   • Use focused Rust tests for changed runtime modules.
   • Use pair-specific tests for translation changes.

   Verify: The smallest relevant check passes before broader validation.

   Docs Maintenance
3. 3

   Expand for user-visible behavior

   Goal: Cover proxy and streaming paths that users actually hit.

   Do

   • Run e2e checks for route, provider, normalization, streaming, capture, or request/response behavior changes.
   • For streaming, include terminal events, incomplete tool streams, stalls, and Unicode boundaries when relevant.

   Verify: The broader command passes or failures are understood and scoped.

   Streaming Internals

Common commands

just site check
cargo fmt --check
pixi run cargo clippy --lib --tests -- -D warnings
pixi run cargo test --lib
just test-e2e
just check

Use the exact project recipes from the root justfile and site/justfile; do not invent new validation commands in docs unless they are added to the repository.