Hey Erik, First, I dont think this is off topic at all, great question! :) To answer it specificly, I dont make tests for private/protected methods. The reasoning is that the tests are there to verify behavior of the object and it's publicly available methods. If the public methods make calls to private/protected methods as part of creating that behavior, then wether that code is functioning as expected or not will become pretty apparent with the test results. Also, I dont usually make private/protected methods for the sake of making them. Rather, I find they're usually the result of a refactoring where I have broken down a public method into smaller pieces either for better legibility or so those pieces can be re-used from other methods, etc.
I have in the past though, gone in and changed the scope of methods to public when trying to test legacy code so that I could narrow my own scope when solving some problems, then changing them back when satisfied. -Mike _______________________________________________ agavi-dev mailing list [email protected] http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
