Write Rust unit, integration, async, and property-based tests following TDD methodology.
npx skills add https://github.com/Femad-6/my-skills --skill rust-testing-femad-6
Please help me install this Agent Skill. Skill: rust-testing Source: https://github.com/Femad-6/my-skills/tree/main/.github/skills/rust-testing Command: npx skills add https://github.com/Femad-6/my-skills --skill rust-testing-femad-6
todo!() placeholders and #[cfg(test)] modules. - Full Testing Stack Coverage: Patterns for unit tests, integration tests in tests/, async tests with #[tokio::test], doc tests, parameterized tests with rstest, property-based tests with proptest, and mocking with mockall. - Coverage and CI Integration: Commands for cargo-llvm-cov with threshold enforcement and a ready-to-use GitHub Actions workflow including fmt, clippy, tests, and coverage gates. - Use Case: When adding a new feature to a Rust crate, use this Skill to write a failing test first, mock repository traits with mockall, validate inputs with proptest strategies, and enforce 80% line coverage in CI. ## Quick Start Ask the assistant to write tests for a Rust function or module following TDD, for example: write unit tests with rstest cases and mockall mocks for my UserService.High-intent search queries and answers about installing and using this skill.
Place tests in a `#[cfg(test)]` module inside the same file as your code, annotate each test function with `#[test]`, and use assertion macros like `assert_eq!` and `assert!`. Run them with `cargo test`.
Apply the `#[automock]` attribute to your trait, then create a mock instance and set expectations with methods like `expect_find_by_id().with(eq(42)).times(1).returning(...)`. Inject the mock into the service under test to isolate it from real dependencies.
rstest provides parameterized tests where you explicitly list input cases with `#[case]` attributes, plus fixture injection. proptest generates random inputs from strategies to verify properties hold across many cases, such as roundtrip or ordering invariants.
Replace `#[test]` with `#[tokio::test]` and mark the function `async`. You can then await futures directly and use utilities like `tokio::time::timeout` to verify timeout behavior without blocking the test runner.
Install cargo-llvm-cov and run `cargo llvm-cov` for a summary, `--html` for a report, or `--fail-under-lines 80` to enforce a threshold. It integrates into CI via the taiki-e/install-action GitHub Action.
Avoid `#[should_panic]` when the function returns a `Result`, since asserting `result.is_err()` or matching specific error variants gives more precise failure information. Reserve `#[should_panic(expected = "...")]` for genuine panic conditions only.
chenziyang110Generates and diagnoses Rust tests using rstest, mockall, tokio, and cargo tooling.
fusengineStructure Cargo workspaces and build Rust CI pipelines with fmt, clippy, cargo-deny, nextest, and coverage.
matteocervelliRun rustfmt, clippy, cargo check, test, and audit for Rust quality gates.
multiversxAutomate property-based testing and fuzzing for MultiversX smart contracts.