Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
aeondave/rust-testingReverse engineering e fuzzing

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 installazioni+3 in 7 giorni39 StelleMITsincronizzato 11 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/rust-testing

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
8EoNHY+dZI…fr/nNVCA==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto088d5f16…83195b8d
088d5f16478f…f19583195b8d8 file · ⁦10.3 KB⁩
ScansioneBasso1 segnalazione
  • Link a domini esterni
Vedi la scansione completa
Sorgentegithub.com/AeonDave/malskill/tree/main/coding/rust-testing@21cd568

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

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-development when implementing persistent code or bug fixes test-first.
  • Pair with testing-reliability for mock/timing anti-patterns and systematic-debugging when 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.

  1. Start with focused unit/integration tests for the behavior change.
  2. Run targeted commands before full-suite reruns.
  3. Stabilize async/boundary tests via explicit timeouts and local fixtures.
  4. Add property/snapshot tests when they increase signal, not just volume.
  5. 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 under tests/, when picking rstest over table loops, should_panic discipline, or trybuild compile-fail tests
  • references/async-and-boundaries.md — use when testing async code, time, IO, and network boundaries
  • references/property-snapshot-and-mocks.md — use when example-based tests are not enough, when output is bulky, or when scripting mockall expectations
  • references/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/OnceLock re-entry
  • references/coverage-and-ci.md — use when wiring coverage, nextest profiles, mutation testing, or stable CI gates
  • references/commands.md — use for the most common Rust test commands and selectors

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellSìSì
Usa la reteSìSì
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

  1. InfoLink · Link a domini esterni

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.11.13-21cd56813 nov 202621cd568088d5f16Firmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login