[Please do not mail me a copy of your followup] boost-users@lists.boost.org spake the secret code <CABUeae8M_S7z1OWcHz9C73Sk7wBfp2nSdK9qodevJBE0roTeJg@mail.gmail.com> thusly:
During retrospection of the big thread on Boost.Test future [1],
Holy crap! How can they talk about killing a library *only* on the developer's list? This would affect *tons* of people, including myself, since I regularly advocate Boost.Test for doing TDD in C++. This seems really unlike what I have come to consider from the Boost folks.
I found this curious post by Gennadiy [2] about mock_object. I had no idea such facility lives in Boost.Test and it looks it's been there for very long time.
Unfortunately I would not recommend it because it is basically undocumented. I would instead recommend using another mock object library in conjunction with Boost.Test such as googlemock or Turtle.
Is the mock_object an internal feature or is it dedicated (and ready) to use by Boost.Test users?
My opinion: no
What are basic features of this mocking facility?
My opinion: who knows, since it's not documented.
How does it compare to Turtle or googlemock?
My opinion: who knows, since it's not documented. -- "The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline> The Computer Graphics Museum <http://computergraphicsmuseum.org> The Terminals Wiki <http://terminals.classiccmp.org> Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com>