Skip to content
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-testingReporting and 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 installs+3 in 7 days39 StarsMITsynced 11 hours ago

Install

No NotHoly CLI yet? Install it first.

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

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
AhbSJJQ+zZ…L2mUZzBg==The CLI checks the SHA-256 and the signature before it writes a file.
Package80499e86…c2b6fc26
80499e863041…5131c2b6fc265 files · ⁦5.5 KB⁩
ScanMedium2 findings
  • injection.no_confirmationreferences/test-design.md:8
  • Links to outside domains
See the full scan
Sourcegithub.com/AeonDave/malskill/tree/main/coding/cpp-testing@21cd568

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

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesYesYes
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumPrompt injection · injection.no_confirmationreferences/test-design.md:8
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.11.13-21cd568Nov 13, 202621cd56880499e86Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login