aeondave/cpp-testing
coding/cpp-testing/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add aeondave/malskill cpp-testingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 5, 2026, 4:12 AM230.2s5 files scanned
SKILL.md
- name:
- cpp-testing
- description:
- 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.
- license:
- MIT
- compatibility:
- C++20 baseline. Tools: CMake 3.20+, CTest. Recommended: GoogleTest. Debugging: gdb/lldb/Valgrind (Linux/macOS), MinGW gdb + objdump (Windows), MSVC dumpbin + WinDbg (Windows). Optional: sanitizers (Clang/GCC/MSVC), coverage (llvm-cov or lcov).
- author:
- AeonDave
- version:
- 1.1
C++ Testing
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
Related Skills
aeondave/unicorn
development
VerifiedTrustedCommunity
Auth/lab ref: Unicorn Engine CPU-only emulation for shellcode, decryptors, custom VM handlers, instruction tracing, memory hooks, and register-level experiments.
11SKILL.mdUpdated Jul 24, 2026
aeondave/renode
development
VerifiedTrustedCommunity
Auth/lab ref: Renode board and SoC simulation for MCU/RTOS firmware, UART/GPIO/peripheral modeling, GDB remote debugging, REPL platforms, and RESC scripts.
11SKILL.mdUpdated Jul 24, 2026
aeondave/qiling
development
VerifiedTrustedCommunity
Auth/lab ref: Qiling OS-layer binary emulation for PE/ELF/Mach-O/UEFI/shellcode with rootfs, syscall/API hooks, filesystem mapping, and runtime patching.
11SKILL.mdUpdated Jul 24, 2026
aeondave/qemu
databases
VerifiedTrustedCommunity
Auth/lab ref: QEMU user-mode and full-system emulation for cross-arch binaries, firmware, kernels, disks, serial consoles, networking, and GDB stubs.
11SKILL.mdUpdated Jul 24, 2026