rust-unit-tests

Automate writing and running unit tests for Warp Rust crates.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/89jobrien/warpx --skill rust-unit-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-unit-tests
Source: https://github.com/89jobrien/warpx/tree/main/.agents/skills/rust-unit-tests
Command: npx skills add https://github.com/89jobrien/warpx --skill rust-unit-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps Rust developers add, refine, and execute unit tests within Warp crates, ensuring code quality and maintainability.

Core Features & Use Cases

  • Focused, crate-level tests that validate individual functions or behaviors.
  • Guidance on where to place tests, how to name test modules, and how to run tests with cargo.
  • Real-world example: adding a test for a utility function to prevent regression.

Quick Start

Create a focused unit test for a single function and run cargo test to confirm it passes.

Frequently Asked Questions about rust-unit-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write and run Rust unit tests for Warp crates?

To run Rust unit tests for Warp crates, you create test files named ${filename}_tests.rs or mod_tests.rs containing a trailing tests module, then execute them using the standard cargo test command.

Where should I place Rust unit tests in my Warp crate modules?

Rust unit tests in Warp crates should live in dedicated files named ${filename}_tests.rs or mod_tests.rs, structured within a trailing tests module to keep test logic isolated from production code.

Can I use #[should_panic] and #[test] attributes when adding unit tests to Warp crates?

Yes, writing Rust unit tests for Warp crates fully supports conventional testing patterns, allowing you to use both standard #[test] and #[should_panic] attributes to validate function behaviors and expected failures.

What is the best way to automate adding focused unit tests to individual Rust functions?

Automating focused Rust unit tests involves generating crate-level tests in designated _tests.rs files that exercise individual functions or modules, preventing code regression and ensuring maintainability.

Does this approach to Rust unit testing require any external testing dependencies or crates?

No external testing dependencies are required to write and run these Rust unit tests, as the process enforces conventional Rust testing patterns and relies entirely on the built-in cargo test runner.

Why are my Rust unit tests not being discovered when running cargo test in my Warp crate?

Rust unit tests may not be discovered if they are not placed in the expected ${filename}_tests.rs or mod_tests.rs files, or if they lack the required trailing tests module structure.