cpp-testing

Topics in the source

• C++ Testing (Agent Skill)
• When to Use
• When NOT to Use
• Core Concepts
• TDD Workflow
• Code Examples
• Basic Unit Test (gtest)
• Fixture (gtest)

Agent-focused testing workflow for modern C++ (C++17/20) using GoogleTest/GoogleMock with CMake/CTest. Writing new C++ tests or fixing existing tests Designing unit/integration test coverage for C++ components Adding test coverage, CI gating, or regression protection Configuring CMake/CTest workflows for consistent execution Investigating test failures or flaky behavior Enabling sanitizers for memory/race diagnostics Implementing new product features without test changes Large-scale refactors unrelated to test coverage or failures Performance tuning without test regressions to validate Non-C++ projects or non-test tasks TDD loop: red → green → refactor (tests first, minimal fix, then cleanups). Isolation: prefer dependency injection and fakes over global state. Test layout: tests/unit, tests/integration, tests/testdata. Mocks vs fakes: mock for interactions, fake for stateful behavior. CTest discovery: use gtestdiscovertests() for stable test discovery. CI signal: run subset first, then full suite with --output-on-failure. Follow the RED → GREEN → REFACTOR loop: 1. RED: write a failing test that captures the new behavior 2. GREEN: implement the smallest change to pass 3. REFACTOR:

This is an excerpt. Refer to the complete source and its current requirements.