I\'m building a class library that will have some public & private methods. I want to be able to unit test the private methods (mostly while developing, but also it coul
In my opinion you should only unit test your classe's public API.
Making a method public, in order to unit test it, breaks encapsulation exposing implementation details.
A good public API solves an immediate goal of the client code and solves that goal completely.