Click here to Skip to main content
13,096,399 members (52,160 online)

Comments by Prafulla Hunde (Top 3 by date)

Prafulla Hunde 3-Jun-15 14:26pm View
Reason for my vote of 5 \n Great !
Prafulla Hunde 25-Mar-11 17:11pm View
I agree that the public interface has to be tested. But if one public method depends on n numbers of private methods to accomplish the task , then skipping them is also not a good idea.The one of the advantage of unit tests is to quickly figure out the failure when code is updated. If public method fails by updating any of private method it will take more time to figure out which one is causing problem. But if private methods are also have tests for them the fix may be quicker.
Prafulla Hunde 25-Mar-11 17:00pm View
Readability may not be so bad if the partial class definition is in separate file.Something like what visual studio does by making Form.Designer.cs to put all auto generated code. Also a separate inner test class can be used to put all testing code.
And all the code in the separate partial class file is compiled conditionally so it does not exist in release dlls.

Advertise | Privacy |
Web02 | 2.8.170813.1 | Last Updated 1 Jan 1900
Copyright © CodeProject, 1999-2017
All Rights Reserved. Terms of Service
Layout: fixed | fluid