Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
aeondave/rust-testingIngeniería inversa y 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 instalaciones+3 en 7 días39 EstrellasMITsincronizado hace 11 horas

Instalar

¿Aún no tienes la CLI de NotHoly? Instálala primero.

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

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
8EoNHY+dZI…fr/nNVCA==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete088d5f16…83195b8d
088d5f16478f…f19583195b8d8 archivos · ⁦10.3 KB⁩
EscaneoBajo1 hallazgo
  • Enlaces a dominios externos
Ver el escaneo completo
Fuentegithub.com/AeonDave/malskill/tree/main/coding/rust-testing@21cd568

Esta entrada todavía no está escrita en tu idioma, así que aparece en 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

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellSíSí
Usa la redSíSí
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

  1. InfoEnlace · Enlaces a dominios externos

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v2026.11.13-21cd56813 nov 202621cd568088d5f16Firmada–

Pregunta todo lo que tu alcance permite.

Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.

  1. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login