axum-test-transport

Source excerpt starting at line 1.

1---2name: axum-test-transport3description: Choose between in-process `tower::ServiceExt::oneshot` tests and real `tokio::net::TcpListener` server tests for Axum services in this repository.4metadata:5  internal: true6---7 8Use this skill when working on Axum tests that currently start a server or could be simplified.9 10Prefer `oneshot` when the test only verifies:11 12- status codes13- headers14- JSON/body shape15- route or middleware behavior16- request handling without real network behavior17 18Use:19 20```rust21use tower::ServiceExt;22```23 24`oneshot` is available through `tower::ServiceExt`.25 26Keep a real `TcpListener` + `axum::serve(...)` when the test needs:27 28- WebSocket upgrade/handshake behavior29- real client behavior (`reqwest`, `tokio_tungstenite`, etc.) as the thing under test30- transport/lifecycle concerns like bind/listen/shutdown31- true end-to-end coverage over `http://` or `ws://`32 33Repository guidance:34 35- `crates/transcribe-cactus/tests/batch.rs` style tests are good `oneshot` candidates36- `crates/transcribe-cactus/tests/live.rs` WebSocket tests should stay real-server37- if several tests share the same in-process request setup, add a tiny local helper (for example request builder or response JSON parser)38 39After changes:40 41- run `pnpm exec dprint fmt`42- run the relevant Rust test compile/check command43