tag:blogger.com,1999:blog-30125454.post115145461579977537..comments2020-05-02T18:54:45.012-07:00Comments on Jacob Carpenter's blogspot: Testing internal codeJacobhttp://www.blogger.com/profile/07300518452274773472noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-30125454.post-1151505060017487282006-06-28T07:31:00.000-07:002006-06-28T07:31:00.000-07:00You know, I hadn't considered that the entire test...You know, I hadn't considered that the entire test assembly now becomes somewhat "omniscient". That's a good point.Jacobhttps://www.blogger.com/profile/07300518452274773472noreply@blogger.comtag:blogger.com,1999:blog-30125454.post-1151483844334900562006-06-28T01:37:00.000-07:002006-06-28T01:37:00.000-07:00The problem with InternalsVisibleTo is that you im...The problem with InternalsVisibleTo is that you immediately loose the "consumer perspective" on the code you're testing. I think this is an important benefit of doing test driven development.<BR/><BR/>I guess one possibility would be to have a separate test assembly for testing internal types. I can't however see myself doing it this way. I find my solutions quickly balloon even with one test assembly per test target (for testing public types).<BR/><BR/>I'm still looking for a good solution to this problem!Anonymousnoreply@blogger.com