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/testing-reliabilityInformes y cumplimiento

testing-reliability

⁨Diagnose flaky tests, misleading mocks or fakes, sleep-based waits, brittle fixtures, test-only production hooks, weak assertions, and mutation-testing gaps. Use when CI behavior differs, tests hide defects, or coverage creates false confidence.⁩

v2026.11.13-21cd5683 instalaciones+3 en 7 días39 EstrellasMITsincronizado hace 10 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/testing-reliability

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

FirmaFirmado, ed25519
2ma6M6hEPa…KEp+iICg==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paqueteeffdd81c…2f090bb3
effdd81ca97c…9e0d2f090bb33 archivos · ⁦5.5 KB⁩
EscaneoMedio3 hallazgos
  • injection.no_confirmationSKILL.md:35
  • Script ejecutable incluido con la skillscripts/find_polluter.py
  • Enlaces a dominios externos
Ver el escaneo completo
Fuentegithub.com/AeonDave/malskill/tree/main/coding-behaviours/testing-reliability@21cd568

Esta entrada todavía no está escrita en tu idioma, así que aparece en English.

Make tests detect the behavior they claim to cover and make failures attributable. Use this skill to repair the test signal; test-driven-development owns the test-first implementation loop.

When to activate

  • Flaky, timing-sensitive, or order-dependent tests.
  • Heavy mocks, unclear patch targets, or fakes that do not match real behavior.
  • Production code changed only to make tests easier.
  • Coverage increased without stronger assertions.
  • Surviving or uncovered mutants in behavior that matters.
  • CI failures that cannot be reproduced locally.

Reliability workflow

  1. Identify the claimed behavior and the misleading result. Preserve the failure evidence or demonstrate a missed defect with the smallest relevant test selection; a local pass does not invalidate a CI failure.
  2. Investigate the relevant source of uncertainty: assertions, test doubles, fixture lifecycle, time, randomness, filesystem/network state, locale, order, or concurrency. Use systematic-debugging when failure attribution or the product defect remains unclear.
  3. Correct that cause. Strengthen an assertion, isolate/reset owned state, repair synchronization, or replace an inaccurate double as needed; do not apply every technique to every test.
  4. Check sensitivity to the defect and preservation of valid behavior. For a double, check the part of the collaborator's contract that matters; choose a real dependency, fake, stub, or mock according to the test's scope and control needs.
  5. Run focused checks and relevant broader tests. Repeat or vary order/schedules when investigating a flake, with a bounded diagnostic purpose; do not rerun until a convenient green result hides failures. Use verification-before-completion for final coverage and freshness.

Anti-patterns to remove

  • Testing incidental internal calls instead of the required behavior or interaction contract.
  • Partial mocks that silently omit important side effects.
  • Sleeping for async behavior instead of waiting on a condition.
  • Shared mutable fixtures that couple tests by order.
  • Golden outputs updated without reviewing semantic changes.
  • Coverage-only tests that assert nothing meaningful.

Offensive testing focus

  • Exploit harnesses must prove primitives, not just crash/no-crash.
  • Fuzz reproducer tests must pin seed/input and minimized artifact.
  • Network tooling tests should use captured transcripts, local test servers, or protocol fakes.
  • Evasion tests must distinguish telemetry absence from collection failure.

Resources

Load on demand:

  • references/testing-anti-patterns.md — load when diagnosing mock/timing failures, coverage without useful assertions, or mutation results.

Scripts:

  • scripts/find_polluter.py — runs matching test files separately and reports the first that leaves a watched filesystem path present. It does not detect in-memory state, changes to existing files, or interactions requiring a sequence of test files; inspect command failures before interpreting a clean result.

Archivos de esta versión

Permisos

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

Hallazgos del escaneo

Revisado el 13 nov 2026

  1. MediaPrompt injection · injection.no_confirmationSKILL.md:35
  2. MediaArchivo · Script ejecutable incluido con la skillscripts/find_polluter.py
  3. 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 202621cd568effdd81cFirmada–

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