在dotnet核心控制器中进行单元测试非公开方法

Question

Suppose in an MVC5 controller I had a method in my controller that gets called by other methods in the controller, but I don't want it available to a user. If I wanted to be able to mock it, it would look like this:

[ChildActionOnly]
public virtual string DoSpecialFormatting(string mySpecialString)
{
    // stuff
}

Or I could have tossed [assembly: InternalsVisibleTo("MyLittleProject.Tests")] and [assembly: InternalsVisibleTo("DynamicProxyGenAssembly2")] (for Moq) into AssemblyInfo.cs and marked the method as internal instead of public :

internal virtual string DoSpecialFormatting(string mySpecialString)
{
    // stuff
}

Now that there is no ChildActionOnly and I don't see an AssemblyInfo.cs file in my new ASP.NET Core project, how would I have methods in my controller class which web users cannot access but can still be mocked?

Answer 1

You can extract that method to a class , ie named SpecialFormatter, and inject to the controller via DI. To test your controller you can mock this class.

class SpecialFormatter
{ 
   public string DoSpecialFormatting(string mySpecialString)
   {
       // stuff
   }
}

Then in your controller

class SomeController : Controller
{

   private SpecialFormatter _formatter;

   public SomeController(SpecialFormatter formatter)
   {
      _formatter = formatter;
   }

   public ActionResult SomeAction(string input)
   {
      string output = _formatter.DoSpecialFormatting(input);
      // stuff
   }

}

Answer 2

In ASP.NET Core the attribute is called NonActionAttribute .

[NonAction]
public virtual string DoSpecialFormatting(string mySpecialString)
{
    // stuff
}

Imho its better than internal.