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/cpp-testingReport 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 installazioni+3 in 7 giorni39 StelleMITsincronizzato 11 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

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

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

FirmaFirmato, ed25519
AhbSJJQ+zZ…L2mUZzBg==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto80499e86…c2b6fc26
80499e863041…5131c2b6fc265 file · ⁦5.5 KB⁩
ScansioneMedio2 segnalazioni
  • injection.no_confirmationreferences/test-design.md:8
  • Link a domini esterni
Vedi la scansione completa
Sorgentegithub.com/AeonDave/malskill/tree/main/coding/cpp-testing@21cd568

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

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
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_confirmationreferences/test-design.md:8
  2. 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 202621cd56880499e86Firmata–

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