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-testingWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package80499e86…c2b6fc26
80499e863041…5131c2b6fc265 files · 5.5 KBScanMedium2 findings
- injection.no_confirmationreferences/test-design.md:8
- Links to outside domains
Sourcegithub.com/AeonDave/malskill/tree/main/coding/cpp-testing@21cd568
On this page
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-developmentwhen implementing persistent code or bug fixes test-first. - Pair with
testing-reliabilityfor mock/timing anti-patterns andsystematic-debuggingwhen symptoms are far from the defect.
Recommended workflow
- Define the behavior and test scope (unit vs integration) first.
- Add/adjust tests with clear Arrange-Act-Assert structure.
- Run focused test selection (
ctest -R/ gtest filter). - Run sanitizers for memory/UB/races where applicable.
- If flaky/failing, minimize reproducer and fix root cause before broad reruns.
Triage loop for failing tests
- Reproduce deterministically on one test binary.
- Capture failure class: assertion mismatch, crash, timeout, data race, UB.
- Narrow input/state until minimal failing case is obtained.
- Fix production code first (or fixture isolation), then harden test.
- 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 testsreferences/sanitizers-coverage.md— ASan/UBSan/TSan + coverage recipesreferences/flakes-debugging.md— anti-flake rules, gdb/lldb, Valgrind, MinGW objdump/nm, MSVC dumpbin/WinDbg, sanitizer env vars
Files in this version
references/49.2 KB
- flakes-debugging.md3.0 KB
- googletest-cmake.md2.1 KB
- sanitizers-coverage.md1.8 KB
- test-design.md2.3 KB
- SKILL.md2.9 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | Yes | Yes |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumPrompt injection · injection.no_confirmationreferences/test-design.md:8
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | Nov 13, 2026 | 21cd568 | 80499e86 | Signed | – |
More from AeonDave
All from this publisherMore in Reporting and compliance
See the category- skillduty1g/skill5
- rea-ci-tests-auditmorluto/rea-ci-tests-audit4
- tracking-threat-actor-infrastructuremukul975/tracking-threat-actor-infrastructure4
- performing-authenticated-scan-with-openvasmukul975/performing-authenticated-scan-with-openvas4
- slicing-code-contexttrailofbits/slicing-code-context4
- 1337aeondave/13374
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login