rust-unit-tests

Rust unit tests in Warp should be placed in files named ${filename}_tests.rs or mod_test.rs, included at the end of the corresponding source file. This modular test structure ensures reliable test coverage across Warp components.

Run Rust unit tests for Warp components using cargo nextest. After creating or updating your unit test module alongside the Rust source, cargo nextest executes the tests to verify behavior and prevent regressions.

Write async unit tests in Warp crates using tokio-compatible test attributes and lightweight patterns. This approach provides guidance on async tests and test isolation to correctly verify asynchronous behavior across Warp components.

Yes, the Warp unit testing approach requires descriptive test names and specific file naming conventions like ${filename}_tests.rs. It also enforces using assert macros for clearer diffs and minimizing global state to improve testability.

Minimizing global state in Rust unit tests improves testability and test isolation. The Warp testing conventions enforce this practice alongside using assert macros for clearer diffs and descriptive naming to ensure reliable test coverage.

Yes, you can use cargo nextest to test individual Warp crates. The approach applies to crate-level tests, enforcing conventions for test file naming, module inclusion, and test attributes across Warp components to prevent regressions.