Agent skill

Cpp Testing

by xu-xiang in xu-xiang/everything-claude-code-zh

仅在编写/更新/修复 C++ 测试、配置 GoogleTest/CTest、诊断失败或不稳定的测试、或添加覆盖率/检测器(Sanitizers)时使用。

MITAuto-check passedTesting & QA

Install Cpp Testing

skills CLI
$ npx skills add xu-xiang/everything-claude-code-zh --skill cpp-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install xu-xiang/everything-claude-code-zh cpp-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/xu-xiang/everything-claude-code-zh.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cpp-testing .claude/skills/cpp-testing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cpp-testing
GitHub stars
2k
Token cost
~1.8k tokens
SKILL.md length
172 words
Files
1
Skills in repo
78
Repo updated
First seen
Licence
MIT

At a glance

仅在编写/更新/修复 C++ 测试、配置 GoogleTest/CTest、诊断失败或不稳定的测试、或添加覆盖率/检测器(Sanitizers)时使用。

  • Works in 3 steps: 红(RED):编写一个捕获新行为的失败测试。 → 绿(GREEN):实施最小化的更改以使测试通过。 → 重构(REFACTOR):在保持测试为绿色的前提下进行清理。
  • Testing & QA work in your project
  • SKILL.md covers 适用场景, 核心概念, TDD 工作流 and 代码示例, plus 8 more sections
  • Calls cmake; reaches github.com

What it does

Cpp Testing is an agent skill from xu-xiang/everything-claude-code-zh. 仅在编写/更新/修复 C++ 测试、配置 GoogleTest/CTest、诊断失败或不稳定的测试、或添加覆盖率/检测器(Sanitizers)时使用。

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA. It works with C++. The repository describes itself as: everything-claude-code 中文翻译项目:完整的 Claude Code 配置集合(agents, skills, hooks, commands, rules, MCPs)。源自 Anthropic 黑客松获胜者的实战配置,助力中文工程师高效理解与使用 Claude Code。 The licence is MIT.

When your agent uses it

  • Testing & QA work in your project

Example prompts

  • “/cpp-testing”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. 红(RED):编写一个捕获新行为的失败测试。
  2. 绿(GREEN):实施最小化的更改以使测试通过。
  3. 重构(REFACTOR):在保持测试为绿色的前提下进行清理。

What it can do on your machine

Read from SKILL.md and the folder at commit dfbf946. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • cmake

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cpp Testing loads about 1.8k tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 172 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~22
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from xu-xiang/everything-claude-code-zh at commit dfbf946, republished under its MIT licence (© xu-xiang). 172 words, ~1,819 tokens.

Download SKILL.mdSave it as .claude/skills/cpp-testing/SKILL.md (or your agent's skills folder).
name
cpp-testing
description
仅在编写/更新/修复 C++ 测试、配置 GoogleTest/CTest、诊断失败或不稳定的测试、或添加覆盖率/检测器(Sanitizers)时使用。
origin
ECC

C++ 测试(智能体技能)

针对现代 C++ (C++17/20) 的智能体测试工作流,使用 GoogleTest/GoogleMock 配合 CMake/CTest。

适用场景

  • 编写新的 C++ 测试或修复现有测试
  • 为 C++ 组件设计单元/集成测试覆盖
  • 添加测试覆盖、CI 门禁或回归防护
  • 配置 CMake/CTest 工作流以实现一致性执行
  • 调查测试失败或不稳定(Flaky)行为
  • 启用检测器(Sanitizers)进行内存/竞态诊断
不适用场景
  • 实施不涉及测试更改的新产品功能
  • 与测试覆盖或失败无关的大规模重构
  • 在没有测试回归验证的情况下进行性能调优
  • 非 C++ 项目或非测试任务

核心概念

  • TDD 循环:红(Red)→ 绿(Green)→ 重构(Refactor)(测试先行,最小化修复,然后清理)。
  • 隔离性:优先选择依赖注入和伪造对象(Fakes),而非全局状态。
  • 测试布局:tests/unit、tests/integration、tests/testdata。
  • Mocks vs Fakes:Mock 用于交互验证,Fake 用于有状态的行为模拟。
  • CTest 发现:使用 gtest_discover_tests() 进行稳定的测试发现。
  • CI 信号:先运行子集,然后使用 --output-on-failure 运行完整套件。

TDD 工作流

遵循 红 → 绿 → 重构 循环:

  1. 红(RED):编写一个捕获新行为的失败测试。
  2. 绿(GREEN):实施最小化的更改以使测试通过。
  3. 重构(REFACTOR):在保持测试为绿色的前提下进行清理。
cpp
// tests/add_test.cpp
#include <gtest/gtest.h>

int Add(int a, int b); // 由生产代码提供。

TEST(AddTest, AddsTwoNumbers) { // 红(RED)
  EXPECT_EQ(Add(2, 3), 5);
}

// src/add.cpp
int Add(int a, int b) { // 绿(GREEN)
  return a + b;
}

// 重构(REFACTOR):一旦测试通过,简化/重命名代码

代码示例

基础单元测试 (gtest)
cpp
// tests/calculator_test.cpp
#include <gtest/gtest.h>

int Add(int a, int b); // 由生产代码提供。

TEST(CalculatorTest, AddsTwoNumbers) {
    EXPECT_EQ(Add(2, 3), 5);
}
测试固件 (Fixture) (gtest)
cpp
// tests/user_store_test.cpp
// 伪代码存根:请将 UserStore/User 替换为项目实际类型。
#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)
cpp
// 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 快速入门
cmake
# CMakeLists.txt (节选)
cmake_minimum_required(VERSION 3.20)
project(example LANGUAGES CXX)

set(CMAKE_CXX_STANDARD 20)
set(CMAKE_CXX_STANDARD_REQUIRED ON)

include(FetchContent)
# 优先使用项目锁定的版本。如果使用 tag,请根据项目策略使用固定版本。
set(GTEST_VERSION v1.17.0) # 根据项目策略调整。
FetchContent_Declare(
  googletest
  # Google Test 框架 (官方仓库)
  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)

enable_testing()
include(GoogleTest)
gtest_discover_tests(example_tests)
bash
cmake -S . -B build -DCMAKE_BUILD_TYPE=Debug
cmake --build build -j
ctest --test-dir build --output-on-failure

运行测试

bash
ctest --test-dir build --output-on-failure
ctest --test-dir build -R ClampTest
ctest --test-dir build -R "UserStoreTest.*" --output-on-failure
bash
./build/example_tests --gtest_filter=ClampTest.*
./build/example_tests --gtest_filter=UserStoreTest.FindsExistingUser

调试失败用例

  1. 使用 gtest 过滤器重新运行单个失败的测试。
  2. 在失败的断言周围添加作用域日志(Scoped Logging)。
  3. 启用检测器(Sanitizers)重新运行。
  4. 根本原因修复后,扩展到运行完整套件。

覆盖率 (Coverage)

优先使用目标级(Target-level)设置,而非全局标志。

cmake
option(ENABLE_COVERAGE "Enable coverage flags" OFF)

if(ENABLE_COVERAGE)
  if(CMAKE_CXX_COMPILER_ID MATCHES "GNU")
    target_compile_options(example_tests PRIVATE --coverage)
    target_link_options(example_tests PRIVATE --coverage)
  elseif(CMAKE_CXX_COMPILER_ID MATCHES "Clang")
    target_compile_options(example_tests PRIVATE -fprofile-instr-generate -fcoverage-mapping)
    target_link_options(example_tests PRIVATE -fprofile-instr-generate)
  endif()
endif()

GCC + gcov + lcov:

bash
cmake -S . -B build-cov -DENABLE_COVERAGE=ON
cmake --build build-cov -j
ctest --test-dir build-cov
lcov --capture --directory build-cov --output-file coverage.info
lcov --remove coverage.info '/usr/*' --output-file coverage.info
genhtml coverage.info --output-directory coverage

Clang + llvm-cov:

bash
cmake -S . -B build-llvm -DENABLE_COVERAGE=ON -DCMAKE_CXX_COMPILER=clang++
cmake --build build-llvm -j
LLVM_PROFILE_FILE="build-llvm/default.profraw" ctest --test-dir build-llvm
llvm-profdata merge -sparse build-llvm/default.profraw -o build-llvm/default.profdata
llvm-cov report build-llvm/example_tests -instr-profile=build-llvm/default.profdata

检测器 (Sanitizers)

cmake
option(ENABLE_ASAN "Enable AddressSanitizer" OFF)
option(ENABLE_UBSAN "Enable UndefinedBehaviorSanitizer" OFF)
option(ENABLE_TSAN "Enable ThreadSanitizer" OFF)

if(ENABLE_ASAN)
  add_compile_options(-fsanitize=address -fno-omit-frame-pointer)
  add_link_options(-fsanitize=address)
endif()
if(ENABLE_UBSAN)
  add_compile_options(-fsanitize=undefined -fno-omit-frame-pointer)
  add_link_options(-fsanitize=undefined)
endif()
if(ENABLE_TSAN)
  add_compile_options(-fsanitize=thread)
  add_link_options(-fsanitize=thread)
endif()

不稳定测试(Flaky Tests)防护准则

  • 永远不要使用 sleep 进行同步;请使用条件变量(Condition Variables)或门闩(Latches)。
  • 确保临时目录在每个测试中都是唯一的,并且始终进行清理。
  • 在单元测试中避免依赖真实时间、网络或文件系统。
  • 为随机输入使用确定性的种子。

最佳实践

建议(DO)
  • 保持测试的确定性和隔离性
  • 优先使用依赖注入而非全局变量
  • 使用 ASSERT_* 检查前提条件,使用 EXPECT_* 进行多重检查
  • 在 CTest 标签或目录中区分单元测试与集成测试
  • 在 CI 中运行检测器以进行内存和竞态检测
禁止(DON'T)
  • 不要在单元测试中依赖真实时间或网络
  • 当可以使用条件变量时,不要使用 sleep 进行同步
  • 不要过度打桩(Mock)简单的值对象(Value Objects)
  • 不要对非关键日志使用脆弱的字符串匹配
常见陷阱
  • 使用固定的临时路径 → 为每个测试生成唯一的临时目录并清理。
  • 依赖墙上时钟时间(Wall clock time) → 注入时钟或使用伪造的时间源。
  • 不稳定的并发测试 → 使用条件变量/门闩和有界等待。
  • 隐藏的全局状态 → 在测试固件中重置全局状态,或移除全局变量。
  • 过度 Mock → 优先对有状态行为使用 Fake,仅对交互使用 Mock。
  • 缺失检测器运行 → 在 CI 中添加 ASan/UBSan/TSan 构建。
  • 仅在 Debug 构建中进行覆盖率统计 → 确保覆盖率目标使用一致的标志。

可选附录:模糊测试 / 属性测试

仅在项目已支持 LLVM/libFuzzer 或属性测试库时使用。

  • libFuzzer:最适合具有极少 I/O 的纯函数。
  • RapidCheck:基于属性的测试,用于验证不变量。

最小化的 libFuzzer 挂钩(伪代码:请替换 ParseConfig):

cpp
#include <cstddef>
#include <cstdint>
#include <string>

extern "C" int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
    std::string input(reinterpret_cast<const char *>(data), size);
    // ParseConfig(input); // 项目函数
    return 0;
}

GoogleTest 的替代方案

  • Catch2:仅头文件,具有表现力的匹配器(Matchers)
  • doctest:轻量级,极小的编译开销

© xu-xiang, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/cpp-testing of xu-xiang/everything-claude-code-zh.

Open the folder on GitHubat commit dfbf946

Compare with similar skills

Cpp Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cpp Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cpp Testing this skillxu-xiang/everything-claude-code-zh2k—~1.8kAutomated safety check: PassMIT
Staticphp Build Troubleshootingcrazywhalecc/static-php-cli1.9k—~814Automated safety check: PassMIT
OpenROAD Module Test AdderThe-OpenROAD-Project/OpenROAD3.2k—~1.8kAutomated safety check: PassBSD-3-Clause
PlotJuggler Live VerificationPlotJuggler/PlotJuggler6.2k—~956Automated safety check: PassMPL-2.0
Run Integration Testsvalkey-io/valkey-search145—~511Automated safety check: PassBSD-3-Clause
TDDFastLED/FastLED7.5k—~848Automated safety check: PassMIT

Similar skills

  • Staticphp Build Troubleshooting

    crazywhalecc/static-php-cli

    Diagnose StaticPHP v3 failures. An agent skill from crazywhalecc/static-php-cli.

    1.9k GitHub stars~814 tokensUpdated today
    Testing & QAAuto-check passed
  • OpenROAD Module Test Adder

    The-OpenROAD-Project/OpenROAD

    Adds integration or unit tests to an OpenROAD module: writes the Tcl test, generates golden files and registers it in both CMake and Bazel.

    3.2k GitHub stars~1.8k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • PlotJuggler Live Verification

    PlotJuggler/PlotJuggler

    Confirms that a change to PlotJuggler 4 really works in the running app by proving the rebuild, launching with real data and measuring the result.

    6.2k GitHub stars~956 tokensUpdated 6 days ago
    Testing & QAAuto-check passed
  • Run Integration Tests

    valkey-io/valkey-search

    Run or troubleshoot Valkey Search C++ and Python integration tests, including focused development runs, full-suite verification, and packaging/build or runtime failure classification.

    145 GitHub stars~511 tokensUpdated today
    Testing & QAAuto-check passed
  • TDD

    FastLED/FastLED

    Guide Test-Driven Development workflow for FastLED. An agent skill from FastLED/FastLED.

    7.5k GitHub stars~848 tokensUpdated today
    Testing & QAAuto-check passed
  • Build Gplates

    GPlates/GPlates

    Configure, build and test the GPlates desktop application. An agent skill from GPlates/GPlates.

    154 GitHub stars~750 tokensUpdated yesterday
    Testing & QAAuto-check passed

More from xu-xiang/everything-claude-code-zh

All 78 skills in this repo
  • Configure Ecc

    xu-xiang/everything-claude-code-zh

    Everything Claude Code 的交互式安装程序 — 引导用户选择并安装技能和规则到用户级或项目级目录,验证路径,并可选择优化已安装文件。

    2k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed
  • Continuous Learning V2

    xu-xiang/everything-claude-code-zh

    基于本能(Instinct)的学习系统,通过钩子(hooks)观察会话,创建带有置信度评分的原子本能,并将其演化为技能(Skills)、命令(Commands)或智能体(Agents)。v2.1 版本增加了项目作用域(project-scoped)的本能,以防止跨项目污染。

    2k GitHub stars~2.1k tokensUpdated 7 mo ago
    Auto-check passed
  • API Design

    xu-xiang/everything-claude-code-zh

    生产级 API 的 REST API 设计模式,包括资源命名、状态码、分页、过滤、错误响应、版本控制和速率限制. An agent skill from xu-xiang/everything-claude-code-zh.

    2k GitHub stars~2.7k tokensUpdated 7 mo ago
    Auto-check passed
  • Backend Patterns

    xu-xiang/everything-claude-code-zh

    后端架构模式、API 设计、数据库优化以及适用于 Node.js、Express 和 Next.js API 路由的服务端最佳实践。

    2k GitHub stars~3.2k tokensUpdated 7 mo ago
    Auto-check passed
  • Backend Patterns

    xu-xiang/everything-claude-code-zh

    后端架构模式、API 设计、数据库优化以及 Node.js、Express 和 Next.js API 路由的服务端最佳实践。

    2k GitHub stars~3.1k tokensUpdated 7 mo ago
    Auto-check passed
  • Backend Patterns

    xu-xiang/everything-claude-code-zh

    后端架构模式、API 设计、数据库优化以及针对 Node.js、Express 和 Next.js API 路由的服务端最佳实践。

    2k GitHub stars~3.2k tokensUpdated 7 mo ago
    Auto-check passed

Works with

Categories

Questions about Cpp Testing

What does Cpp Testing do?

仅在编写/更新/修复 C++ 测试、配置 GoogleTest/CTest、诊断失败或不稳定的测试、或添加覆盖率/检测器(Sanitizers)时使用。. Cpp Testing is an agent skill from xu-xiang/everything-claude-code-zh.

When should I use Cpp Testing?

Cpp Testing fits situations like: testing & QA work in your project.

How do I install Cpp Testing in Claude Code?

Run `npx skills add xu-xiang/everything-claude-code-zh --skill cpp-testing -a claude-code`. Or copy the skill folder (skills/cpp-testing in xu-xiang/everything-claude-code-zh) into .claude/skills/cpp-testing in your project. Claude Code loads it when a task matches its description.

How do I install Cpp Testing in Codex?

Run `npx skills add xu-xiang/everything-claude-code-zh --skill cpp-testing -a codex`. Or copy the skill folder (skills/cpp-testing in xu-xiang/everything-claude-code-zh) into .agents/skills/cpp-testing in your project. Codex loads it when a task matches its description.

Can I use Cpp Testing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add xu-xiang/everything-claude-code-zh --skill cpp-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cpp-testing, .gemini/skills/cpp-testing, .github/skills/cpp-testing and .opencode/skills/cpp-testing in your project.

What does Cpp Testing need to run?

Going by SKILL.md and its folder, Cpp Testing needs the command-line tools its instructions call (cmake).

Does Cpp Testing access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Cpp Testing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cpp Testing use?

Cpp Testing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cpp Testing use?

About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cpp Testing?

Skills that share tags, products or a category with Cpp Testing: Staticphp Build Troubleshooting (crazywhalecc/static-php-cli, 1.9k stars), OpenROAD Module Test Adder (The-OpenROAD-Project/OpenROAD, 3.2k stars), PlotJuggler Live Verification (PlotJuggler/PlotJuggler, 6.2k stars) and Run Integration Tests (valkey-io/valkey-search, 145 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cpp Testing?

xu-xiang (a GitHub user) maintains it in xu-xiang/everything-claude-code-zh, which has 1,971 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on March 5, 2026.

Source: xu-xiang/everything-claude-code-zh on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.