skills.rest
llmh333
llmh333COMMUNITY
Explore all skills by this author →
GitHub

cpp-testing

Diagnose and fix failing C++ tests with GoogleTest and CMake/CTest.

Updated Sep 13, 2025
Search Tags:#testing#debugging#c++#cmake#sanitizers#ctest#googletest
One-click install
npx skills add https://github.com/llmh333/employee_management_spring --skill cpp-testing-llmh333
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cpp-testing
Source: https://github.com/llmh333/employee_management_spring/tree/main/.gemini/skills/cpp-testing
Command: npx skills add https://github.com/llmh333/employee_management_spring --skill cpp-testing-llmh333

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

C++ test failures and flaky behavior slow down development by breaking CI confidence, wasting debugging time, and hiding regressions. This skill helps you reliably diagnose and correct test issues while improving test coverage and stability.

Core Features & Use Cases

  • GoogleTest/GoogleMock workflows: Write unit and integration tests, including fixtures and mocks for interaction verification.
  • CMake/CTest execution patterns: Configure builds and run tests consistently using CTest, including stable discovery.
  • Debugging and hardening: Diagnose failing tests, reduce flakiness with deterministic practices, and add sanitizers/coverage to surface hidden defects.

Quick Start

Use the cpp-testing skill to investigate and fix the failing test case by running the appropriate CTest target, then narrowing down with a focused GoogleTest filter and rerunning with output on failure until the root cause is corrected.

Frequently Asked Questions about cpp-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix flaky GoogleTest failures in CMake CTest?▼

Fix flaky C++ tests by running the specific CTest target, narrowing down with focused GoogleTest filters, and rerunning with output on failure until the root cause is corrected. This enforces deterministic test isolation and stable gtest discovery.

What causes flaky C++ tests and how do sanitizers help?▼

Flaky C++ tests stem from non-deterministic behavior and hidden memory defects. Applying sanitizers and coverage instrumentation during CTest execution surfaces these hidden defects, enabling you to diagnose failures and harden tests for reliable CI gating.

Can I use GoogleMock for integration testing with CMake?▼

Yes, you can use GoogleMock with CMake for integration testing by writing unit and integration tests that utilize fixtures and mocks for interaction verification. This is configured through stable CTest and gtest discovery patterns.

What's the best way to configure CTest for stable test discovery?▼

The best way to configure CTest for stable test discovery is to ensure CMake properly registers GoogleTest cases for consistent execution. Stable CTest and gtest discovery prevents CI breaking and hides regressions during automated test execution.

Why does my C++ test workflow require deterministic test isolation?▼

C++ test workflows require deterministic test isolation to prevent flaky behavior from breaking CI confidence and hiding regressions. Hardening tests with deterministic practices and sanitizers ensures reliable debugging and stable regression protection.

Related Skills

Explore More Software Engineering Skills→
mbadozmbadoz
2

cpp-testing

Automate C++ test setup, execution, and validation with GoogleTest/CTest and CMake.

Community
Advanced
steven715steven715
2

tdd-workflow

Enforce test-driven development in C++ projects using Google Test and CMake/CTest.

Community
Intermediate
ShankulkarniShankulkarni
1

audit-vibecode-patterns

Detects AI-generated slop patterns in JavaScript/TypeScript codebases.

Community
Intermediate
riftzen-bitriftzen-bit

cpp-testing

Diagnose and fix C++ test failures using GoogleTest/CMake/CTest.

Community
Advanced