cpp11 branch - turning away from one header philosophy

[mrAtari]

IMHO one of the unique advantages of hippomocks is the tiny one-header include.

I totally agree, that different classes / aspects should be separated, especially if you want to keep the code clean and maintainable. On the other hand, it's a big advantage having one single file to keep a low barrier and enhance acceptance of non TDD developers.
I would reallly appreciate, to keep the one-header approach, it is especially helpful to setup TDD classes or programming dojos with teams (e.g. on cyber-dojo.org).

[dascandy]

It is an in-development thing. The intent is to merge these parts so that it's still a single-header for users, while at the same time making it easier to integrate on both sides of the chain - on one hand prepackaged for various package formats, on the other hand with reporters for various test frameworks.

[mrAtari]

Superb.
The idea with the reporters is a great one. That's what I have on my todo list next. Check if it can be easily extended

[dascandy]

Please do look at the cpp11 branch - it has detail/reporter.h which is the interface, and detail/defaultreporter.h which is the one that does what you can expect from before. It's already in there for you to use :-)