Question 1

How do I integrate FakeIt with Catch2?

Accepted Answer

Add the single_header/catch folder to your include path; FakeIt is pre-configured for Catch2 v2 and v3, automatically integrating assertions into your test output without extra setup.

Question 2

Can FakeIt mock classes with unique_ptr or other smart pointers?

Accepted Answer

Yes, but on MSVC, you must enable Edit And Continue debug mode (/ZI) for proper mocking of destructors, as noted in the README limitations for smart pointers.

Question 3

FakeIt or Google Mock: which is better for C++ unit testing?

Accepted Answer

FakeIt excels with its header-only design and simpler API, reducing boilerplate, while Google Mock offers more features like thread safety and better support for complex inheritance. Choose FakeIt for quick setup and expressiveness, Google Mock for advanced scenarios.

Question 4

How to spy on an existing object using FakeIt?

Accepted Answer

Instantiate a Mock template pointing to the object, such as Mock<SomeInterface> spy(obj), allowing you to intercept and verify calls to 'obj' in one line without modifying the original code.

Question 5

Does FakeIt work with C++17 or newer standards?

Accepted Answer

FakeIt is written in C++11 and can be used with C++11 and later projects, but it doesn't explicitly leverage newer language features; compatibility relies on compiler support for C++11 semantics.

Question 6

What if my unit testing framework isn't listed in the configurations?

Accepted Answer

Use the standalone configuration by including the single_header/standalone folder, but you'll need to handle assertions manually without the automated integration provided for pre-configured frameworks.

FakeIt

What is FakeIt?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions