cpp-unit-testing

Generate and augment C++ unit tests using GoogleTest patterns.

3|2|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/sentenz/skills --skill cpp-unit-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cpp-unit-testing
Source: https://github.com/sentenz/skills/tree/main/skills/cpp-unit-testing
Command: npx skills add https://github.com/sentenz/skills --skill cpp-unit-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates generation and augmentation of C++ unit tests using GoogleTest (GTest) with established patterns.

Core Features & Use Cases

  • Automates generation and augmentation of GTest-based unit tests across src and tests directories.
  • Supports common testing patterns (In-Got-Want, Table-Driven, AAA) and phrasing for quick adoption.
  • Use Case: When adding or modifying a module, generate a complete test scaffold that matches project conventions and ensures coverage by default.

Quick Start

Create a GoogleTest-based unit test suite for the target C++ module following In-Got-Want, AAA, and table-driven patterns.

Frequently Asked Questions about cpp-unit-testing

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

FAQPage Schema
How do I generate GoogleTest unit tests for a C++ module?

Generate GoogleTest unit tests by automating test scaffolding across src and tests directories, applying established patterns to ensure immediate module coverage matching project conventions.

What is the AAA pattern in C++ unit testing?

The AAA pattern in C++ unit testing structures tests into Arrange, Act, and Assert phases, providing a standardized template to organize GoogleTest execution logic and assertions.

How do I use table-driven tests with GoogleTest?

Table-driven tests with GoogleTest separate test data from test logic, iterating through input datasets to validate C++ behavior across multiple parameters and expected outputs comprehensively.

Can I augment existing C++ unit test suites without rewriting them?

You can augment existing C++ unit test suites by integrating new pattern-based templates directly into current files, specifically targeting and updating modules named using the *_test.cpp convention.

Does this approach work with existing C++ project directory structures?

This approach works directly with existing C++ project structures by automatically scanning and applying GoogleTest generation patterns across your established src and tests directories.