Comments on: How to unit test private methods in C# using NUnit http://iserialized.com/unit-testing-private-methods-in-c-using-nunit-and-reflection/ .Net, C#, Scrum and agile software development Fri, 20 Jan 2012 10:25:12 +0000 hourly 1 http://wordpress.org/?v=3.1.1 By: Paul Eie http://iserialized.com/unit-testing-private-methods-in-c-using-nunit-and-reflection/comment-page-1/#comment-113 Paul Eie Thu, 08 Apr 2010 18:35:11 +0000 http://iserialized.com/?p=66#comment-113 This blog post is a direct result of my own experience on this. I have used this in several projects, and I'm very satisfied with the solution! The unit tests classes become somewhat hard to read, but I'd rather prefer that over not unit testing private methods or worse, changing them to public methods just to be able to test them! This blog post is a direct result of my own experience on this. I have used this in several projects, and I’m very satisfied with the solution!

The unit tests classes become somewhat hard to read, but I’d rather prefer that over not unit testing private methods or worse, changing them to public methods just to be able to test them!

]]> By: typo http://iserialized.com/unit-testing-private-methods-in-c-using-nunit-and-reflection/comment-page-1/#comment-111 typo Wed, 07 Apr 2010 23:36:22 +0000 http://iserialized.com/?p=66#comment-111 You have tested it and writing form your personal experience or you find some information online? You have tested it and writing form your personal experience or you find some information online?

]]> By: Kris Krause http://iserialized.com/unit-testing-private-methods-in-c-using-nunit-and-reflection/comment-page-1/#comment-110 Kris Krause Wed, 07 Apr 2010 20:38:04 +0000 http://iserialized.com/?p=66#comment-110 "it's easier to force developers to use a class correct if I only expose the necessary methods for the class to work correctly" If you want to do this, them force them through an interface. “it’s easier to force developers to use a class correct if I only expose the necessary methods for the class to work correctly”

If you want to do this, them force them through an interface.

]]> By: Paul Eie http://iserialized.com/unit-testing-private-methods-in-c-using-nunit-and-reflection/comment-page-1/#comment-48 Paul Eie Fri, 12 Mar 2010 08:59:40 +0000 http://iserialized.com/?p=66#comment-48 I guess I would have solved it somewhat different I had used Visual Studio's test tool, but what I like about the reflection approach is that I don't have to change my original file or any configuration to make it work. But still, it's rather dirty to read in the reflection approach ;) I guess I would have solved it somewhat different I had used Visual Studio’s test tool, but what I like about the reflection approach is that I don’t have to change my original file or any configuration to make it work.

But still, it’s rather dirty to read in the reflection approach ;)

]]> By: Dagfinn http://iserialized.com/unit-testing-private-methods-in-c-using-nunit-and-reflection/comment-page-1/#comment-47 Dagfinn Fri, 12 Mar 2010 08:03:06 +0000 http://iserialized.com/?p=66#comment-47 Reflection is always a good last resort :) Having had just the same problem recently (but Visual Studio's test tool, not NUnit), I found two other ways of doing it. 1- Have Visual Studio generate a private accessor http://msdn.microsoft.com/en-us/library/ms184807.aspx 2- Defining InternalsVisibleToAttribute as part of the assembly definition http://msdn.microsoft.com/en-us/library/system.runtime.compilerservices.internalsvisibletoattribute.aspx Cheers Reflection is always a good last resort :)

Having had just the same problem recently (but Visual Studio’s test tool, not NUnit), I found two other ways of doing it.

1- Have Visual Studio generate a private accessor
http://msdn.microsoft.com/en-us/library/ms184807.aspx

2- Defining InternalsVisibleToAttribute as part of the assembly definition
http://msdn.microsoft.com/en-us/library/system.runtime.compilerservices.internalsvisibletoattribute.aspx

Cheers

]]>