18 Nov
2007
18 Nov
'07
5:29 p.m.
Robert Ramey wrote:
Joel de Guzman wrote:
Hmm - and implementation details shouldn't be documented? shouldn't be tested? If they're in a common area it seems that they are meant to be used by more than one library - and indeed they are. lightweight test others come to mind.
If they are public or protected they should be documented for end-users and other developers respectively. What should be tested is the public interface, which is normally enough to test whether the protected and private implementation is working properly.