Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
aeondave/testing-reliabilityRelatórios 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 instalações+3 em 7 dias39 EstrelasMITsincronizado há 10 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

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

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
2ma6M6hEPa…KEp+iICg==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacoteeffdd81c…2f090bb3
effdd81ca97c…9e0d2f090bb33 arquivos · ⁦5.5 KB⁩
VarreduraMédio3 achados
  • injection.no_confirmationSKILL.md:35
  • Script executável junto com a skillscripts/find_polluter.py
  • Links para domínios externos
Ver a varredura completa
Fontegithub.com/AeonDave/malskill/tree/main/coding-behaviours/testing-reliability@21cd568

Este item ainda não foi escrito no seu idioma, então aparece em 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.

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosSimSim
Grava arquivosSimSim
Roda comandos no shellSimSim
Usa a redeSimSim
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

  1. MédiaPrompt injection · injection.no_confirmationSKILL.md:35
  2. MédiaArquivo · Script executável junto com a skillscripts/find_polluter.py
  3. InfoLink · Links para domínios externos

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.11.13-21cd56813 de nov. de 202621cd568effdd81cAssinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login