How to test internal class library?

问题:

I would like to write a class library which creates for me a complex object but should only be exposed as little as possible. I want it to be included into other projects and there I only have one call to this library which e.g. returns me an object of a internally created class. I don't want to allow others to create these objects explicitly, but still I want to create a test project for this class library.

For example:

var result = Manager.Instance.Create(definition)

This should be the only access to the class library.

Based on the definition parameter it uses different sub classes to create the requested instance and sets its properties accordingly. Therefore I want to assure somehow by tests that the whole creation process worked fine. But since I also don't want to expose very little internal properties of the result object too I cannot test by only using this public access method since I don't have any properties to assert on.

I know that you should not test for internal mechanics and it is typically bad design and I also was reading through this article, but isn't there maybe any way to create a library plus unit test project and maybe afterwards limit the access to this class? with a wrapper or something?

回答1:

In .NET can use the InternalsVisibleToAttribute in your class library to make your internal types visible to your unit test project.

That way you can keep your class internal and still use it from other assemblies that you give access.

You use it like this:

[assembly:InternalsVisibleTo("NameOfYourUnitTestProject")]

回答2:

For the latest csproj 2017 formated projects, if your project does not have the AssemblyInfo.cs file, you can add the following:

  <ItemGroup>
    <AssemblyAttribute Include="System.Runtime.CompilerServices.InternalsVisibleTo">
      <_Parameter1>$(MSBuildProjectName).Tests</_Parameter1>
    </AssemblyAttribute>
  </ItemGroup>

You also can use other variables to relplace MSBuildProjectName such as AssemblyName or use the unittest project name directly.

You can check the ProjectName.AssemblyInfo.cs in obj folder (obj\Debug\netstandard2.0) has been updated by adding InternalsVisibleTo.