cpp-testing

Modern C++ testing workflow using GoogleTest/GoogleMock with CMake/CTest integration.

affaan-m/everything-claude-code|Updated May 13, 2026

Works with

Claude CodeCursorClineWindsurfCodexGoose

What it does

Covers unit and integration test design with TDD red-green-refactor loop, fixtures, mocks, and fakes for dependency isolation
Includes CMake/CTest configuration with automatic test discovery via gtest_discover_tests() and filtering strategies
Provides coverage setup for GCC (gcov/lcov) and Clang (llvm-cov), plus sanitizer configuration (ASan, UBSan, TSan) for memory and race detection
Documents f

Repository

affaan-m/everything-claude-code

Last updated

May 13, 2026

Installation Guide

Select your AI agent

How to use cpp-testing on Cursor

AI-first code editor with Composer

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

›Cursor installed and configured on your machine
›Node.js 16+ with npm — verify with node --version
›Active project directory where you want to add cpp-testing

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/affaan-m/everything-claude-code --skill cpp-testing

Fetches cpp-testing from affaan-m/everything-claude-code and configures it for Cursor.

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?

│

│ ── Universal (.agents/skills) ────────────────

│ · Cline · Codex · Goose · Windsurf

│ ●Cursor(selected)

│ · Cursor · Aider · Continue

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/cpp-testing

Restart Cursor to activate cpp-testing. Access via /cpp-testing in your agent's command palette.

⚠

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

›View source on GitHub ›Skills CLI docs ›About Cursor ›What are agent skills?

Documentation

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

✓

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

✓

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

✓

Improve work quality by 30-40% with less effort

When to Use

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

When NOT to Use

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

Core Concepts

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 gtest_discover_tests() for stable test discovery.

CI signal: run subset first, then full suite with --output-on-failure.

TDD Workflow

Follow the RED → GREEN → REFACTOR loop:

RED: write a failing test that captures the new behavior

GREEN: implement the smallest change to pass

REFACTOR: clean up while tests stay green

// tests/add_test.cpp #include <gtest/gtest.h> int Add(int a, int b); // Provided by production code. TEST(AddTest, AddsTwoNumbers) { // RED EXPECT_EQ(Add(2, 3), 5); } // src/add.cpp int Add(int a, int b) { // GREEN return a + b; } // REFACTOR: simplify/rename once tests pass

Code Examples

Basic Unit Test (gtest)

// tests/calculator_test.cpp #include <gtest/gtest.h> int Add(int a, int b); // Provided by production code. TEST(CalculatorTest, AddsTwoNumbers) { EXPECT_EQ(Add(2, 3), 5); }

Fixture (gtest)

// tests/user_store_test.cpp // Pseudocode stub: replace UserStore/User with project types. #include <gtest/gtest.h> #include <memory> #include <optional> #include <string> struct User { std::string name; }; class UserStore { public: explicit UserStore(std::string /*path*/) {} void Seed(std::initializer_list<User> /*users*/) {} std::optional<User> Find(const std::string &/*name*/) { return User{"alice"}; } }; class UserStoreTest : public ::testing::Test { protected: void SetUp() override { store = std::make_unique<UserStore>(":memory:"); store->Seed({{"alice"}, {"bob"}}); } std::unique_ptr<UserStore> store; }; TEST_F(UserStoreTest, FindsExistingUser) { auto user = store->Find("alice"); ASSERT_TRUE(user.has_value()); EXPECT_EQ(user->name, "alice"); }

Mock (gmock)

// tests/notifier_test.cpp #include <gmock/gmock.h> #include <gtest/gtest.h> #include <string> class Notifier { public: virtual ~Notifier() = default; virtual void Send(const std::string &message) = 0; }; class MockNotifier : public Notifier { public: MOCK_METHOD(void, Send, (const std::string &message), (override)); }; class Service { public: explicit Service(Notifier &notifier) : notifier_(notifier) {} void Publish(const std::string &message) { notifier_.Send(message); } private: Notifier &notifier_; }; TEST(ServiceTest, SendsNotifications) { MockNotifier notifier; Service service(notifier); EXPECT_CALL(notifier, Send("hello")).Times(1); service.Publish("hello"); }

CMake/CTest Quickstart

# CMakeLists.txt (excerpt) cmake_minimum_required(VERSION 3.20) project(example LANGUAGES CXX) set(CMAKE_CXX_STANDARD 20) set(CMAKE_CXX_STANDARD_REQUIRED ON) include(FetchContent) # Prefer project-locked versions. If using a tag, use a pinned version per project policy. set(GTEST_VERSION v1.17.0) # Adjust to project policy. FetchContent_Declare( googletest # Google Test framework (official repository) URL https://github.com/google/googletest/archive/refs/tags/${GTEST_VERSION}.zip ) FetchContent_MakeAvailable(googletest) add_executable(example_tests tests/calculator_test.cpp src/calculator.cpp ) target_link_libraries(example_tests GTest::gtest GTest::gmock GTest::gtest_main)

cpp-testing

What it does

Category

Repository

Last updated

Installation Guide

How to use cpp-testing on Cursor

Prerequisites

Run the install command

Select Cursor when prompted

Verify installation

Security Notice

Documentation

List & Monetize Your Skill

Use Cases

Task Automation & Efficiency

Knowledge Enhancement

Quality Improvement

Install Skill

C++ Testing (Agent Skill)

When to Use

When NOT to Use

Core Concepts

TDD Workflow

Code Examples

Basic Unit Test (gtest)

Fixture (gtest)

Mock (gmock)

CMake/CTest Quickstart

Implementation Guide

Best Practices

When to Use This

Learning Path

Related Skills

java-coding-standards

video-editing

prompt-optimizer

market-research

continuous-learning-v2

django-patterns

Reviews

Discussion

`Implementation Guide`

`Best Practices`

`When to Use This`

`Learning Path`

`Related Skills`

`Reviews`

`Discussion`