Accessor provides access to private/protected methods, members, properties, and events. It does not provide access to private/protected classes within your class. And private/protected classes (TypeB) are intended to be used only by methods of owning class (TypeA). So basically you are trying to add private class (TypeB) from outside of TypeA to 'myList' which is private. Since you are using accessor, there is no problem to access myList.

NSpec is a battle hardened testing framework for C# that's heavily inspired by Mocha and RSpec. It has a fancy logo, is released under the MIT License, and is an. Jan 26, 2017. Popular C# unit testing frameworks. The unit testing frameworks I'll be testing are: NUnit; XUnit; Built-in Visual Studio testing tools. All of these unit testing frameworks offer a similar end goal, to help make writing unit tests faster, simpler and easier! But there are still a few key differences between them.

However you can not use TypeB through accessor. Posiible solution would be to move TypeB outside of TypeA. But it can break your design. How Is Cheese Made. – Apr 8 '13 at 22:23.

Yes, don't Test private methods. The idea of a unit test is to test the unit by its public 'API'. If you are finding you need to test a lot of private behavior, most likely you have a new 'class' hiding within the class you are trying to test, extract it and test it by its public interface. One piece of advice / Thinking tool. There is an idea that no method should ever be private. Meaning all methods should live on a public interface of an object. If you feel you need to make it private, it most likely lives on another object.

This piece of advice doesn't quite work out in practice, but its mostly good advice, and often it will push people to decompose their objects into smaller objects. When you've been dumped on an OO codebase so horrifically designed and asked to 'incrementally improve it', it was a disappointment to find I couldn't had some first tests for private methods. Yeh, perhaps in the textbooks these methods wouldn't be here, but in the real world we have users who have product requirements. I can't just do a massive 'Look at ma clean code' refactoring without getting some tests in the project to build off. Feels like another instance of forcing practising programmers into avenues that naively seem good, but fail to take account of real messy shit. – Apr 24 at 9:51. “There is nothing called as standard or best practice, probably they are just popular opinions”.