C++ Testing
Modern C++ testing workflow: GoogleTest/GoogleMock, CMake/CTest, TDD loop, flaky-test diagnosis, sanitizers, and coverage.
- What
- Modern C++ testing workflow: GoogleTest/GoogleMock, CMake/CTest, TDD loop, flaky-test diagnosis, sanitizers, and coverage.
- Cost
- Free
- Needs
- Use "C++ Testing" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: an agent-focused testing workflow for modern C++ (C++17/20) built on GoogleTest and GoogleMock with CMake/CTest. It teaches the red-green-refactor TDD loop, test isolation through dependency injection and fakes instead of global state, the tests/unit-tests/integration-testdata layout, and when to mock (interactions) versus fake (stateful behavior). CI guidance covers running a subset first, then the full suite with output on failure, plus sanitizers for memory and race diagnostics. It even tells you when NOT to use it (feature work without test changes, pure performance tuning), which is rarer and more useful than it sounds. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: pure guidance, nothing to install; assumes a CMake-based C++ project with GoogleTest available; sanitizer sections need a compatible toolchain. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "C++ Testing" with your Muse. Prerequisites: a CMake-based C++ project with GoogleTest/GoogleMock available. Pure guidance skill, nothing to install. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/cpp-testing/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Review these C++ tests against this workflow: isolation, mock-vs-fake choice, TDD discipline." 3. For new tests, ask: "Write GoogleTest tests for this component following the red-green-refactor loop, with fakes for stateful dependencies." Tip: run the subset first, then the full suite with --output-on-failure; use gtest_discover_tests() for stable discovery. Safety: a skill is plain-text instructions; it runs nothing by itself. Never paste secrets into a chat, and review anything Muse proposes before it changes your code.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.