On 9/21/05, J. Erik Heinz <[EMAIL PROTECTED]> wrote: > > 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 > hmm. i have a little different opinion. I am a fan off automated test > [i would love to use "cruise control", but sadly its just for java :(], > thats why i want a test for every function. If something goes wrong, i > just know in which function.
We were using DamageControl for a while, http://damagecontrol.codehaus.org/ you might play with that. I dont think it changes my reasoning though. I make a change, and run the tests locally and only commit working code so the build shouldnt break. -Mike _______________________________________________ agavi-dev mailing list [email protected] http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
