I don’t like GMock. It’s not as if it was badly written or designed. But it lets you to unit-test dirtier code, tying to method call structure instead of resulting data. For instance, this GMock code can be rewritten:
A friend asked me for it, so probably someone might need a jumpstart in unit tests. Here’s a short list of short (though very deep, if not best) intros. Except for JUnit cookbook (~2 pages) (which has a lot of “ports”, like CppUnit cookbook), I’d name: “Endo-Testing: Unit Testing with Mock Objects” at mockobjects.com (Tim […]
Comparison of Microsoft Visual Studio unit tests (MSTest) vs NUnit, mentioning PartCover and
