Well, you could use some SFINAE and static_asserts to give a better description of the interface and possible usage

I think that HippoMocks actually solves it way better than Mockaron+GoogleMock since you don’t need to add anything to your code like macros. It just hooks the the wanted functionclass in-memory with a very elegant and easy to use interface.

Yes we’re trying it on our projects and so far it’s giving encouraging results. The next thing I’d like to do it integrate it with Google Mock like you did.

Hi, Philippe here! Nice post, and nice solution. One inconvenient I see is that you basically need to compile your code twice (once per .templ.cpp), but maybe it’s a small price to pay. It seems to me that this solution can be extended to handle the example case in my presentation by making the whole class template. And you don’t even need C++11/14!
Anyway, I think it’s a good solution. Have you tried it in a real project? I would be interested in your feedback if you do 🙂

Yep I was at the meetup 🙂 Indeed Mockaron answers the same need but with macro and not templates. And I’ll certainly show this to Philippe to collect his feedback.
Thanks for your suggestions about concepts and modules – it will definitely be worth digging in that direction when they become more widely available!

By the way, to me, it looks a lot like a mock. Another solution presented at today’s C++ Meetup is Mockaron, which has a quite different approach.

Good point Vladislav, it would be nice to find a way to express in the interface what types should be used.

Thanks Karl! I mostly use gtest and you’re right, testing is related to the refactoring necessary to improve the expressiveness of existing code, so it would make for a good topic. Thanks for the suggestion.