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/testing-reliabilityReport e compliance

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

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

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

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

FirmaFirmato, ed25519
2ma6M6hEPa…KEp+iICg==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchettoeffdd81c…2f090bb3
effdd81ca97c…9e0d2f090bb33 file · ⁦5.5 KB⁩
ScansioneMedio3 segnalazioni
  • injection.no_confirmationSKILL.md:35
  • Script eseguibile incluso nella skillscripts/find_polluter.py
  • Link a domini esterni
Vedi la scansione completa
Sorgentegithub.com/AeonDave/malskill/tree/main/coding-behaviours/testing-reliability@21cd568

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: 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.

File di questa versione

Permessi

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

Segnalazioni della scansione

Rivisto il 13 nov 2026

  1. MediaPrompt injection · injection.no_confirmationSKILL.md:35
  2. MediaFile · Script eseguibile incluso nella skillscripts/find_polluter.py
  3. 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 202621cd568effdd81cFirmata–

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