CODEWITHSUNDEEP
c#visual-studiounit-testingaccess-levels
Matt Kline
Matt Kline

Reputation: 10487

Protection Levels and Visual Studio unit tests with C#

I am setting up some unit tests for a C# project I'm working on, and I opted to use Visual Studio's built-in unit test project. The problem is that I have been giving most of my classes in the project the default, internal access level. Now they can't be reached by my unit test project because it is a different assembly.

It would be trivial to just make all my classes in the project public so that the unit test project can access them, but isn't it idiomatic to keep classes which are only used internally by a project internal?

Upvotes: 5

Views: 1667

Answers (2)

fejesjoco
fejesjoco

Reputation: 11903

There is built-in support for that, it's called private accessors. Read about here for example: http://msdn.microsoft.com/en-us/library/bb385974%28v=vs.100%29.aspx

By the way, please consider whether you really want to unit test the internals of a project. According to some schools, you shouldn't do that, but I understand that it can be useful.

Upvotes: 0

NDJ
NDJ

Reputation: 5194

you can make your internals visible to the test project - see here for more info

Upvotes: 4

Related Questions