C++ テストの作成/更新/修正、GoogleTest/CTest の設定、失敗またはフレーキーなテストの診断、カバレッジ/サニタイザーの追加時にのみ使用します。
87
82%
Does it follow best practices?
Impact
92%
1.22xAverage score across 3 eval scenarios
Passed
No known issues
CMake/CTest GoogleTest setup
CMake minimum version
0%
100%
C++ standard 20
0%
0%
CXX_STANDARD_REQUIRED
100%
100%
FetchContent for GoogleTest
100%
100%
Pinned GoogleTest version
100%
100%
gtest_discover_tests used
100%
100%
tests/unit directory
0%
0%
enable_testing called
100%
100%
include(GoogleTest)
100%
100%
GTest link libraries
50%
100%
ctest run command
100%
100%
TDD workflow and mock vs fake usage
TDD order documented
37%
100%
Mock for interaction
0%
100%
Fake for stateful behavior
30%
50%
Dependency injection used
100%
100%
ASSERT_* for preconditions
100%
100%
EXPECT_* for multiple checks
100%
100%
No global state in tests
100%
100%
No over-mocking
100%
100%
No real network/time in unit tests
100%
100%
tests/unit placement
0%
100%
gtest_discover_tests used
0%
100%
Coverage and sanitizer configuration
ENABLE_COVERAGE option
100%
100%
Target-level coverage flags
100%
100%
GCC coverage flags
100%
100%
Clang coverage flags
100%
100%
ENABLE_ASAN option
100%
100%
ENABLE_UBSAN option
100%
100%
ENABLE_TSAN option
100%
100%
Sanitizer flags via add_compile/link_options
66%
100%
lcov/genhtml usage for GCC
100%
100%
llvm-cov usage for Clang
100%
100%
ASan frame pointer flag
100%
100%
5df943e
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.