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.