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/cpp-testingRelatórios e compliance

cpp-testing

⁨C++ testing workflow for unit and integration tests: GoogleTest/GoogleMock, CMake/CTest integration, diagnosing flaky tests, and running sanitizers and coverage for correctness signal. Use when writing or fixing C++ tests and test infrastructure.⁩

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/cpp-testing

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

AssinaturaAssinado, ed25519
AhbSJJQ+zZ…L2mUZzBg==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote80499e86…c2b6fc26
80499e863041…5131c2b6fc265 arquivos · ⁦5.5 KB⁩
VarreduraMédio2 achados
  • injection.no_confirmationreferences/test-design.md:8
  • Links para domínios externos
Ver a varredura completa
Fontegithub.com/AeonDave/malskill/tree/main/coding/cpp-testing@21cd568

Este item ainda não foi escrito no seu idioma, então aparece em English.

High-signal workflow for writing and maintaining reliable C++ tests.

When to activate

  • Adding new unit tests, regression tests, or integration tests
  • Fixing failing or flaky C++ tests
  • Wiring GoogleTest with CMake/CTest
  • Enabling sanitizers for memory/UB/race diagnostics

Outcome expectations

  • Fast deterministic unit tests with clear failure messages.
  • Integration tests separated and labeled by cost/risk.
  • Flake triage follows reproducible, root-cause-first workflow.
  • Sanitizers/coverage are integrated as recurring quality signal.

Core rules

  • Tests must be deterministic: no sleeping for synchronization.
  • Prefer fakes for state, mocks for interactions.
  • Use ASSERT_* for preconditions, EXPECT_* for additional checks.
  • Keep unit tests fast; label integration tests separately.
  • Keep one source of truth for test configuration in CMake targets.
  • Avoid production-only test hooks unless they expose a real design 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 symptoms are far from the defect.

  1. Define the behavior and test scope (unit vs integration) first.
  2. Add/adjust tests with clear Arrange-Act-Assert structure.
  3. Run focused test selection (ctest -R / gtest filter).
  4. Run sanitizers for memory/UB/races where applicable.
  5. If flaky/failing, minimize reproducer and fix root cause before broad reruns.

Triage loop for failing tests

  1. Reproduce deterministically on one test binary.
  2. Capture failure class: assertion mismatch, crash, timeout, data race, UB.
  3. Narrow input/state until minimal failing case is obtained.
  4. Fix production code first (or fixture isolation), then harden test.
  5. Re-run focused + full suite + sanitizer build.

Resources

Load on demand:

  • references/googletest-cmake.md — FetchContent + CTest discovery (gtest_discover_tests)
  • references/test-design.md — unit vs integration, fixtures, parameterized tests
  • references/sanitizers-coverage.md — ASan/UBSan/TSan + coverage recipes
  • references/flakes-debugging.md — anti-flake rules, gdb/lldb, Valgrind, MinGW objdump/nm, MSVC dumpbin/WinDbg, sanitizer env vars

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
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_confirmationreferences/test-design.md:8
  2. 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 202621cd56880499e86Assinada–

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