rust-testing
Rust testing patterns for unit, integration, async, doc, property, snapshot, fuzz, and benchmark-adjacent tests. Use when writing or reviewing tests for `.rs` code, reducing flakiness, designing fixtures/fakes, improving CI confidence, hardening `unsafe`/FFI/parsers with Miri and sanitizers, or test
v2026.11.13-21cd5683 installs+3 in 7 days39 StarsMITsynced 11 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/rust-testingWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package088d5f16…83195b8d
088d5f16478f…f19583195b8d8 files · 10.3 KBScanLow1 finding
- Links to outside domains
Sourcegithub.com/AeonDave/malskill/tree/main/coding/rust-testing@21cd568
On this page
High-signal guidance for Rust tests that are deterministic, maintainable, and worth running.
Use this skill when tests are part of the change, when flakiness needs to die quietly, or when CI needs stronger signal.
When to activate
- Adding unit, integration, async, or doctests for Rust code
- Refactoring brittle or slow Rust tests
- Introducing fakes, mocks, property tests, or snapshot tests
- Tightening CI feedback with coverage, nextest, or command selection
- Hardening parsers,
unsafe, or FFI code against arbitrary input with fuzzing, Miri, or sanitizers - Testing locks, atomics, or shutdown joins (Loom, Miri races, deadlock)
Core rules
- Prefer small unit tests for logic and integration tests for public behavior and boundaries.
- Keep tests deterministic: avoid sleep-based timing and shared mutable global state.
- Use mocks sparingly; prefer fakes, temp dirs, test servers, and controlled inputs.
- Treat doctests as part of the public contract, not decorative comments.
- Coverage is a signal, not the goal; strong assertions beat inflated percentages.
- Avoid production-only test hooks unless they expose a legitimate public or crate-private seam.
- Pair with
test-driven-developmentwhen implementing persistent code or bug fixes test-first. - Pair with
testing-reliabilityfor mock/timing anti-patterns andsystematic-debuggingwhen the root cause is unclear.
Outcome expectations
- Tests are deterministic, debuggable, and fast enough to run frequently.
- Boundaries (time/fs/network/randomness) are explicit and controllable.
- CI separates fast confidence checks from heavier coverage/property/snapshot stages.
Recommended workflow
- Start with focused unit/integration tests for the behavior change.
- Run targeted commands before full-suite reruns.
- Stabilize async/boundary tests via explicit timeouts and local fixtures.
- Add property/snapshot tests when they increase signal, not just volume.
- Verify CI command mix remains fast and reproducible.
Quick review checklist
- Test names describe behavior, not implementation trivia
- Setup is short and local; helpers remove noise without hiding intent
- External boundaries (time, filesystem, network, randomness) are controlled explicitly
- Async tests await real conditions instead of sleeping and hoping
- CI runs the right mix of
cargo test, doctests, and any nextest/coverage steps
Resources
Load on demand:
references/unit-and-integration.md— use when deciding what belongs beside the code vs undertests/, when pickingrstestover table loops,should_panicdiscipline, ortrybuildcompile-fail testsreferences/async-and-boundaries.md— use when testing async code, time, IO, and network boundariesreferences/property-snapshot-and-mocks.md— use when example-based tests are not enough, when output is bulky, or when scriptingmockallexpectationsreferences/fuzzing-and-sanitizers.md— use to hunt panics, memory-safety bugs, and UB on arbitrary input (cargo-fuzz, arbitrary, AFL, Miri, sanitizers)references/concurrency-testing.md— load when testing atomics/Mutex/channels: Loom models, Miri races vs TSan, deadlock/OnceLockre-entryreferences/coverage-and-ci.md— use when wiring coverage, nextest profiles, mutation testing, or stable CI gatesreferences/commands.md— use for the most common Rust test commands and selectors
Files in this version
references/719.9 KB
- async-and-boundaries.md1.8 KB
- commands.md1.5 KB
- concurrency-testing.md4.2 KB
- coverage-and-ci.md2.0 KB
- fuzzing-and-sanitizers.md5.2 KB
- property-snapshot-and-mocks.md2.0 KB
- unit-and-integration.md3.3 KB
- SKILL.md4.1 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | Nov 13, 2026 | 21cd568 | 088d5f16 | Signed | – |
More from AeonDave
All from this publisherMore in Reverse engineering and fuzzing
See the categoryAsk anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login