On 7/16/19 4:41 PM, boB Stepp wrote: > Peter Otten, while responding to one of my questions in the past, > mentioned something in passing that apparently has been mulling around > in the back of my head. I don't recall his exact words, but he > essentially said that I should be testing the public interface to my > classes, but not the methods only used internally by the class and not > meant to be publicly accessible. Is this generally how I should be > viewing testing? Would someone be willing to expand at some length on > this topic?
Test everything (within reason). If you practice TDD, say, where your tests are the contract for how an interface shall behave, that makes a lot more sense for public APIs, which shall not change or be flagged immediately by your unit tests, than for internal functions which should be able to change within reason to suit implementation needs. _______________________________________________ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: https://mail.python.org/mailman/listinfo/tutor
