This document discusses unit testing in C++ using stubs and mocks. It introduces Google Mock as a mocking framework for C++. Mock objects allow specifying expectations of how dependencies will be used in tests. With Google Mock, expectations are set using EXPECT_CALL() and return values specified with actions like Will(). Tests initialize Google Mock and call RUN_ALL_TESTS(). Matchers can specify expected argument values. Cardinalities like Times() specify how many calls should occur. Google Mock allows dependency injection and behavior verification in C++ unit tests.
This document discusses unit testing in C++ using stubs and mocks. It introduces Google Mock as a mocking framework for C++. Mock objects allow specifying expectations of how dependencies will be used in tests. With Google Mock, expectations are set using EXPECT_CALL() and return values specified with actions like Will(). Tests initialize Google Mock and call RUN_ALL_TESTS(). Matchers can specify expected argument values. Cardinalities like Times() specify how many calls should occur. Google Mock allows dependency injection and behavior verification in C++ unit tests.
This document discusses unit testing in C++ using stubs and mocks. It introduces Google Mock as a mocking framework for C++. Mock objects allow specifying expectations of how dependencies will be used in tests. With Google Mock, expectations are set using EXPECT_CALL() and return values specified with actions like Will(). Tests initialize Google Mock and call RUN_ALL_TESTS(). Matchers can specify expected argument values. Cardinalities like Times() specify how many calls should occur. Google Mock allows dependency injection and behavior verification in C++ unit tests.
This document discusses unit testing in C++ using stubs and mocks. It introduces Google Mock as a mocking framework for C++. Mock objects allow specifying expectations of how dependencies will be used in tests. With Google Mock, expectations are set using EXPECT_CALL() and return values specified with actions like Will(). Tests initialize Google Mock and call RUN_ALL_TESTS(). Matchers can specify expected argument values. Cardinalities like Times() specify how many calls should occur. Google Mock allows dependency injection and behavior verification in C++ unit tests.
Your tests are slow as they depend on too many libraries or use expensive resources (e.g. a database). Your tests are brittle as some resources they use are unreliable (e.g. the network, current time). You want to test how your code handles a failure which is not easy to trigger. You need to make sure that your module interacts with other modules in the right way. Dependent Interface Does not yet exist or may change behavior.
5 MOCK OBJECT
A mock object implements the same interface as a real
object (so it can be used as one), but lets you specify at run time how it will be used and what it should do
6 EXPECTATIONS
Use the EXPECT_CALL() macro to set an
expectation on a mock method
7 ACTIONS
The return value of mock functions can be
specified by Will and Return Statement
8 USING GMOCK
include <gmock/gmock.h> write your mocks and tests initialize gmock by InitGoogleMock() call RUN_ALL_TESTS() in main() function compile and run
InitGoogleMock() will automatically initialize Google Test
