# Coverage and verification
This crate is validated with a layered test strategy:
- `cargo test --all-features`
- `cargo test --no-default-features`
- `cargo clippy --all-targets --all-features -- -D warnings`
- `cargo doc --all-features --no-deps`
- `cargo package --allow-dirty --offline`
## Numeric coverage reports
If you want a line/branch coverage report locally, use one of:
- `cargo llvm-cov --all-features --workspace --lcov --output-path target/coverage/lcov.info`
- `cargo tarpaulin --all-features --out Html`
Those tools are not required for the crate itself, but they are useful when
you want a numeric coverage artifact beyond the regression suite.
## What the current suite focuses on
- wire/message parsing
- packet framing and CRC32C
- Hello/Commit/DHPart/Confirm/Ping/SASrelay behavior
- algorithm negotiation and rejection paths
- retained-secret cache behavior
- DH/ECDH and session-secret helpers
- handshake state transitions
- packet-pumped end-to-end secure completion
- `--no-default-features` wire-only builds