Automate creation and verification of Google Mock tests for C++ projects.
npx skills add https://github.com/sentenz/skills --skill cpp-mock-testing
Please help me install this Agent Skill. Skill: cpp-mock-testing Source: https://github.com/sentenz/skills/tree/main/skills/cpp-mock-testing Command: npx skills add https://github.com/sentenz/skills --skill cpp-mock-testing
Automates the creation of mock objects and test scaffolding for C++ projects, enabling reliable isolation of units under test.
Create a GMock-based unit test for a given C++ interface to validate interactions and error handling.
High-intent search queries and answers about installing and using this skill.
GMock automates C++ mock test creation by generating mock objects with MOCK_METHOD macros, enabling precise behavior verification of method calls, arguments, and call counts for isolated unit testing.
The best way to structure C++ mock tests is using the Arrange-Act-Assert (AAA) pattern, enhanced by In-Got-Want and table-driven style templates. This architecture supports both NiceMock and StrictMock patterns for precise verification.
Yes, you can use GMock with CMake and Google Test workflows. The generated mock tests align with CMake, Google Test, and standard build/test runners to integrate seamlessly into typical C++ codebases.
Use StrictMock versus NiceMock in C++ testing to control behavior verification strictness. StrictMock fails on uninteresting calls, while NiceMock ignores them, allowing precise expectations on method calls and arguments.
Automate test scaffolding for C++ interface dependencies by generating GMock-based unit tests that validate interactions and error handling. This creates mock objects and test architecture templates to isolate units under test.
EnigmaWUAutomate C/C++ project setup with CMake, Google Tests, and sanitizers.
mbadozAutomate C++ test setup, execution, and validation with GoogleTest/CTest and CMake.
steven715Enforce test-driven development in C++ projects using Google Test and CMake/CTest.
LusciiReplace real dependencies with mocks, stubs, fakes, or spies in unit tests.
