News for hackers. Stuff that matters.
Re:Anti Patterns Catalog by khedoros1 on Saturday December 31, 2016 @02:52AM (#13290043)
The assumption is that your public members are your interface. Anything private is an internal implementation detail, possibly subject to future change or replacement.

Thorough testing of the public methods should end up calling all of the private methods. Of course, that's a best case scenario. In C++ at least, it'd be an option to make a testing class that's a friend of the class it tests. Then you could test the private members individually.

Re:Anti Patterns Catalog by justicezyx on Saturday December 31, 2016 @11:07PM (#13294666)
I think almost all modern languages end up with granting (unit) testing code free access to everything. The idea of testing only the public interface is about an unique snow flake only meaningful in C++ design, and was never a viable practice at all. Otherwise, I'd say at least one other language follow the similar approach...
Re:Anti Patterns Catalog by khedoros1 on Sunday January 01, 2017 @07:14PM (#13298194)
Are you just complaining about a lack of introspection to get around access controls? Friend classes are better for encapsulation than introspection is.