I think there is, or was, a big debate about this in the testing
community. Personally, I believe in testing public interfaces and use
cases. If the private function is so involved it needs its own test,
it may be a sign that it belongs in another class (possibly not
published, eg its header file is not be exported).
HTH,
Noel
On 3/22/06, Leif Gruenwoldt
Is there a way to test the private functions of a class without moving them into public scope during test?
What are some strategies for this?
I was hoping to add "friend class boost::unit_test::test_suite;" to my class but that didn't work.
-- Leif Gruenwoldt _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users