blocks|key|1353653|text|我希望实现抽象工厂模式。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1353654|为工厂创建一个接口，专门用于提供用户名。|1353655|然后提供具体的类，一个提供User.Identity.Name，另一个提供用于测试的其他硬编码值。|offset|length|style|CODE|1353656|然后，您可以根据生产和测试代码使用适当的具体类。可能希望将工厂作为参数传递，或者根据某些配置值切换到正确的工厂。|1353657|interface+IUserNameFactory
{
++++string+BuildUserName();
}

class+ProductionFactory+:+IUserNameFactory
{
++++public+BuildUserName()+{+return+User.Identity.Name;+}
}

class+MockFactory+:+IUserNameFactory
{
++++public+BuildUserName()+{+return+"James";+}
}

IUserNameFactory+factory;

if(inProductionMode)
{
++++factory+=+new+ProductionFactory();
}
else
{
++++factory+=+new+MockFactory();
}

SettingsViewModel+svm+=+_context.MySettings(factory.BuildUserName());|code-block|syntax|javascript|1353658|entityMap^0|0|0|D|I|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@$F|V|G|W|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|X|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|Y|8|@]|9|@]|A|$O|P]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

I would look to implement an Abstract Factory Pattern. 

Create an interface for a factory specifically for providing user names.

Then provide concrete classes, one which provides <code>User.Identity.Name</code>, and one that provides some other hard coded value that works for your tests.

You can then use the appropriate concrete class depending on production versus test code. Perhaps looking to pass the factory in as a parameter, or switching to the correct factory based on some configuration value.

<pre><code>interface IUserNameFactory
{
 string BuildUserName();
}

class ProductionFactory : IUserNameFactory
{
 public BuildUserName() { return User.Identity.Name; }
}

class MockFactory : IUserNameFactory
{
 public BuildUserName() { return "James"; }
}

IUserNameFactory factory;

if(inProductionMode)
{
 factory = new ProductionFactory();
}
else
{
 factory = new MockFactory();
}

SettingsViewModel svm = _context.MySettings(factory.BuildUserName());
</code></pre>

blocks|key|2654738|text|在以前的版本中，您可以直接在控制器上设置User，这样可以进行一些非常简单的单元测试。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2654739|如果您查看ControllerBase的源代码，您会注意到User是从HttpContext提取的。|2654740|///+<summary>
///+Gets+the+<see+cref="ClaimsPrincipal"/>+for+user+associated+with+the+executing+action.
///+</summary>
public+ClaimsPrincipal+User+=>+HttpContext?.User;|code-block|syntax|javascript|2654741|控制器通过HttpContext访问ControllerContext。|2654742|///+<summary>
///+Gets+the+<see+cref="Http.HttpContext"/>+for+the+executing+action.
///+</summary>
public+HttpContext+HttpContext+=>+ControllerContext.HttpContext;|2654743|您会注意到，这两个属性都是只读属性。好消息是，ControllerContext属性允许设置它的值，因此这将是您的方法。|2654744|所以我们的目标是瞄准那个物体。在核心中，HttpContext是抽象的，因此它更容易模拟。|2654745|假设一个控制器|2654746|public+class+MyController+:+Controller+{
++++IMyContext+_context;

++++public+MyController(IMyContext+context)+{
++++++++_context+=+context;
++++}

++++public+IActionResult+Index()+{
++++++++SettingsViewModel+svm+=+_context.MySettings(User.Identity.Name);
++++++++return+View(svm);
++++}

++++//...other+code+removed+for+brevity+
}|2654747|使用Moq，测试可能如下所示|2654748|public+void+Given_User_Index_Should_Return_ViewResult_With_Model()+{
++++//Arrange+
++++var+username+=+"FakeUserName";
++++var+identity+=+new+GenericIdentity(username,+"");

++++var+mockPrincipal+=+new+Mock<ClaimsPrincipal>();
++++mockPrincipal.Setup(x+=>+x.Identity).Returns(identity);
++++mockPrincipal.Setup(x+=>+x.IsInRole(It.IsAny<string>())).Returns(true);

++++var+mockHttpContext+=+new+Mock<HttpContext>();
++++mockHttpContext.Setup(m+=>+m.User).Returns(mockPrincipal.Object);

++++var+model+=+new+SettingsViewModel()+{
++++++++//...other+code+removed+for+brevity
++++};

++++var+mockContext+=+new+Mock<IMyContext>();
++++mockContext.Setup(m+=>+m.MySettings(username)).Returns(model);

++++var+controller+=+new+MyController(mockContext.Object)+{
++++++++ControllerContext+=+new+ControllerContext+{
++++++++++++HttpContext+=+mockHttpContext.Object
++++++++}
++++};

++++//Act
++++var+viewResult+=+controller.Index()+as+ViewResult;

++++//Assert
++++Assert.IsNotNull(viewResult);
++++Assert.IsNotNull(viewResult.Model);
++++Assert.AreEqual(model,+viewResult.Model);
}|2654749|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/dotnet/aspnetcore/blob/master/src/Mvc/Mvc.Core/src/ControllerBase.cs#L219^0|K|4|0|T|4|Z|B|5|E|0|0|0|5|B|I|H|0|0|N|H|0|K|B|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1D|8|@$9|1E|A|1F|B|C]|$9|1G|A|1H|B|C]]|D|@$9|1I|A|1J|1|1K]]|E|$]]|$1|H|3|I|5|J|7|1L|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1M|8|@$9|1N|A|1O|B|C]|$9|1P|A|1Q|B|C]]|D|@]|E|$]]|$1|O|3|P|5|J|7|1R|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|1S|8|@$9|1T|A|1U|B|C]]|D|@]|E|$]]|$1|S|3|T|5|6|7|1V|8|@$9|1W|A|1X|B|C]]|D|@]|E|$]]|$1|U|3|V|5|6|7|1Y|8|@]|D|@]|E|$]]|$1|W|3|X|5|J|7|1Z|8|@]|D|@]|E|$K|L]]|$1|Y|3|Z|5|6|7|20|8|@]|D|@]|E|$]]|$1|10|3|11|5|J|7|21|8|@]|D|@]|E|$K|L]]|$1|12|3|-4|5|6|7|22|8|@]|D|@]|E|$]]]|13|$14|$5|15|16|17|E|$18|19]]]]

In previous versions you could have set <code>User</code> directly on the controller, which made for some very easy unit tests.

If you look at the source code for <a href="https://github.com/dotnet/aspnetcore/blob/master/src/Mvc/Mvc.Core/src/ControllerBase.cs#L219" rel="noreferrer">ControllerBase</a> you will notice that the <code>User</code> is extracted from <code>HttpContext</code>. 

<pre><code>/// &lt;summary&gt;
/// Gets the &lt;see cref="ClaimsPrincipal"/&gt; for user associated with the executing action.
/// &lt;/summary&gt;
public ClaimsPrincipal User =&gt; HttpContext?.User;
</code></pre>

and the controller accesses the <code>HttpContext</code> via <code>ControllerContext</code>

<pre><code>/// &lt;summary&gt;
/// Gets the &lt;see cref="Http.HttpContext"/&gt; for the executing action.
/// &lt;/summary&gt;
public HttpContext HttpContext =&gt; ControllerContext.HttpContext;
</code></pre>

You will notice that these two are read only properties. The good news is that <code>ControllerContext</code> property allows for setting it's value so that will be your way in.

So the target is to get at that object. In Core <code>HttpContext</code> is abstract so it is a lot easier to mock.

Assuming a controller like

<pre><code>public class MyController : Controller {
 IMyContext _context;

 public MyController(IMyContext context) {
 _context = context;
 }

 public IActionResult Index() {
 SettingsViewModel svm = _context.MySettings(User.Identity.Name);
 return View(svm);
 }

 //...other code removed for brevity 
}
</code></pre>

Using Moq, a test could look like this

<pre><code>public void Given_User_Index_Should_Return_ViewResult_With_Model() {
 //Arrange 
 var username = "FakeUserName";
 var identity = new GenericIdentity(username, "");

 var mockPrincipal = new Mock&lt;ClaimsPrincipal&gt;();
 mockPrincipal.Setup(x =&gt; x.Identity).Returns(identity);
 mockPrincipal.Setup(x =&gt; x.IsInRole(It.IsAny&lt;string&gt;())).Returns(true);

 var mockHttpContext = new Mock&lt;HttpContext&gt;();
 mockHttpContext.Setup(m =&gt; m.User).Returns(mockPrincipal.Object);

 var model = new SettingsViewModel() {
 //...other code removed for brevity
 };

 var mockContext = new Mock&lt;IMyContext&gt;();
 mockContext.Setup(m =&gt; m.MySettings(username)).Returns(model);

 var controller = new MyController(mockContext.Object) {
 ControllerContext = new ControllerContext {
 HttpContext = mockHttpContext.Object
 }
 };

 //Act
 var viewResult = controller.Index() as ViewResult;

 //Assert
 Assert.IsNotNull(viewResult);
 Assert.IsNotNull(viewResult.Model);
 Assert.AreEqual(model, viewResult.Model);
}
</code></pre>

blocks|key|2654797|text|控制器的User+被访问通过控制器的。后一个被储存在ControllerContext中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2654798|设置用户的最简单方法是为构造的用户分配一个不同的HttpContext。我们可以为此目的使用DefaultHttpContext，这样我们就不必什么都模拟了。然后，我们只需在控制器上下文中使用该HttpContext并将其传递给控制器实例：|2654799|var+user+=+new+ClaimsPrincipal(new+ClaimsIdentity(new+Claim[]
{
++++new+Claim(ClaimTypes.Name,+"example+name"),
++++new+Claim(ClaimTypes.NameIdentifier,+"1"),
++++new+Claim("custom-claim",+"example+claim+value"),
},+"mock"));

var+controller+=+new+SomeController(dependencies…);
controller.ControllerContext+=+new+ControllerContext()
{
++++HttpContext+=+new+DefaultHttpContext()+{+User+=+user+}
};|code-block|syntax|javascript|2654800|在创建自己的ClaimsIdentity时，请确保将显式authenticationType传递给构造函数。这将确保IsAuthenticated将正确工作(如果您在代码中使用它来确定用户是否经过身份验证)。|2654801|entityMap|0|LINK|mutability|MUTABLE|url|https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.mvc.controllerbase.user?view=aspnetcore-2.2|1|https://github.com/aspnet/AspNetCore/blob/v2.2.5/src/Mvc/Mvc.Core/src/ControllerBase.cs#L196|2|https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.mvc.controllerbase.httpcontext?view=aspnetcore-2.2|3|https://github.com/aspnet/AspNetCore/blob/v2.2.5/src/Mvc/Mvc.Core/src/ControllerBase.cs#L39|4|https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.mvc.controllercontext?view=aspnetcore-2.2|5|https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.http.defaulthttpcontext?view=aspnetcore-2.2|6|https://learn.microsoft.com/en-us/dotnet/api/system.security.claims.claimsidentity?view=netstandard-2.0|7|https://learn.microsoft.com/en-us/dotnet/api/system.security.claims.claimsidentity.authenticationtype?view=netstandard-2.0|8|https://learn.microsoft.com/en-us/dotnet/api/system.security.claims.claimsidentity.isauthenticated?view=netstandard-2.0^0|4|4|Q|H|4|4|0|9|3|1|E|4|2|M|3|3|Q|H|4|0|1A|I|1A|I|5|0|0|6|E|S|I|1M|F|6|E|6|S|I|7|1M|F|8|0^^$0|@$1|2|3|4|5|6|7|1C|8|@$9|1D|A|1E|B|C]|$9|1F|A|1G|B|C]]|D|@$9|1H|A|1I|1|1J]|$9|1K|A|1L|1|1M]|$9|1N|A|1O|1|1P]|$9|1Q|A|1R|1|1S]|$9|1T|A|1U|1|1V]]|E|$]]|$1|F|3|G|5|6|7|1W|8|@$9|1X|A|1Y|B|C]]|D|@$9|1Z|A|20|1|21]]|E|$]]|$1|H|3|I|5|J|7|22|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|23|8|@$9|24|A|25|B|C]|$9|26|A|27|B|C]|$9|28|A|29|B|C]]|D|@$9|2A|A|2B|1|2C]|$9|2D|A|2E|1|2F]|$9|2G|A|2H|1|2I]]|E|$]]|$1|O|3|-4|5|6|7|2J|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]|W|$5|R|S|T|E|$U|X]]|Y|$5|R|S|T|E|$U|Z]]|10|$5|R|S|T|E|$U|11]]|12|$5|R|S|T|E|$U|13]]|14|$5|R|S|T|E|$U|15]]|16|$5|R|S|T|E|$U|17]]|18|$5|R|S|T|E|$U|19]]|1A|$5|R|S|T|E|$U|1B]]]]

The controller’s <a href="https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.mvc.controllerbase.user?view=aspnetcore-2.2" rel="noreferrer"><code>User</code></a> <a href="https://github.com/aspnet/AspNetCore/blob/v2.2.5/src/Mvc/Mvc.Core/src/ControllerBase.cs#L196" rel="noreferrer">is accessed</a> through the <a href="https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.mvc.controllerbase.httpcontext?view=aspnetcore-2.2" rel="noreferrer"><code>HttpContext</code> of the controller</a>. The latter <a href="https://github.com/aspnet/AspNetCore/blob/v2.2.5/src/Mvc/Mvc.Core/src/ControllerBase.cs#L39" rel="noreferrer">is stored</a> within the <a href="https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.mvc.controllercontext?view=aspnetcore-2.2" rel="noreferrer"><code>ControllerContext</code></a>.

The easiest way to set the user is by assigning a different HttpContext with a constructed user. We can use <a href="https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.http.defaulthttpcontext?view=aspnetcore-2.2" rel="noreferrer"><code>DefaultHttpContext</code></a> for this purpose, that way we don’t have to mock everything. Then we just use that HttpContext within a controller context and pass that to the controller instance:

<pre><code>var user = new ClaimsPrincipal(new ClaimsIdentity(new Claim[]
{
 new Claim(ClaimTypes.Name, "example name"),
 new Claim(ClaimTypes.NameIdentifier, "1"),
 new Claim("custom-claim", "example claim value"),
}, "mock"));

var controller = new SomeController(dependencies…);
controller.ControllerContext = new ControllerContext()
{
 HttpContext = new DefaultHttpContext() { User = user }
};
</code></pre>

When creating your own <a href="https://learn.microsoft.com/en-us/dotnet/api/system.security.claims.claimsidentity?view=netstandard-2.0" rel="noreferrer"><code>ClaimsIdentity</code></a>, make sure to pass an explicit <a href="https://learn.microsoft.com/en-us/dotnet/api/system.security.claims.claimsidentity.authenticationtype?view=netstandard-2.0" rel="noreferrer"><code>authenticationType</code></a> to the constructor. This makes sure that <a href="https://learn.microsoft.com/en-us/dotnet/api/system.security.claims.claimsidentity.isauthenticated?view=netstandard-2.0" rel="noreferrer"><code>IsAuthenticated</code></a> will work correctly (in case you use that in your code to determine whether a user is authenticated).

blocks|key|1355512|text|也有可能使用现有的类，并且只在需要时进行模拟。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1355513|var+user+=+new+Mock<ClaimsPrincipal>();
_controller.ControllerContext+=+new+ControllerContext
{
++++HttpContext+=+new+DefaultHttpContext
++++{
++++++++User+=+user.Object
++++}
};|code-block|syntax|javascript|1355514|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

There is also the possibility to use the existing classes, and mock only when needed.

<pre><code>var user = new Mock&lt;ClaimsPrincipal&gt;();
_controller.ControllerContext = new ControllerContext
{
 HttpContext = new DefaultHttpContext
 {
 User = user.Object
 }
};
</code></pre>

blocks|key|2654844|text|在我的例子中，我需要使用Request.HttpContext.User.Identity.IsAuthenticated、Request.HttpContext.User.Identity.Name和一些位于控制器之外的业务逻辑。我能够结合恩科西、卡林和波克的答案来回答这个问题：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2654845|var+identity+=+new+Mock<IIdentity>();
identity.SetupGet(i+=>+i.IsAuthenticated).Returns(true);
identity.SetupGet(i+=>+i.Name).Returns("FakeUserName");

var+mockPrincipal+=+new+Mock<ClaimsPrincipal>();
mockPrincipal.Setup(x+=>+x.Identity).Returns(identity.Object);

var+mockAuthHandler+=+new+Mock<ICustomAuthorizationHandler>();
mockAuthHandler.Setup(x+=>+x.CustomAuth(It.IsAny<ClaimsPrincipal>(),+...)).Returns(true).Verifiable();

var+controller+=+new+MyController(...);

var+mockHttpContext+=+new+Mock<HttpContext>();
mockHttpContext.Setup(m+=>+m.User).Returns(mockPrincipal.Object);

controller.ControllerContext+=+new+ControllerContext();
controller.ControllerContext.HttpContext+=+new+DefaultHttpContext()
{
++++User+=+mockPrincipal.Object
};

var+result+=+controller.Get()+as+OkObjectResult;
//Assert+results

mockAuthHandler.Verify();|code-block|syntax|javascript|2654846|entityMap^0|C|1D|1Q|12|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|L|$]]

In my case, I needed to make use of <code>Request.HttpContext.User.Identity.IsAuthenticated</code>, <code>Request.HttpContext.User.Identity.Name</code> and some business logic sitting outside of the controller. I was able to use a combination of Nkosi's, Calin's and Poke's answer for this:

<pre><code>var identity = new Mock&lt;IIdentity&gt;();
identity.SetupGet(i =&gt; i.IsAuthenticated).Returns(true);
identity.SetupGet(i =&gt; i.Name).Returns("FakeUserName");

var mockPrincipal = new Mock&lt;ClaimsPrincipal&gt;();
mockPrincipal.Setup(x =&gt; x.Identity).Returns(identity.Object);

var mockAuthHandler = new Mock&lt;ICustomAuthorizationHandler&gt;();
mockAuthHandler.Setup(x =&gt; x.CustomAuth(It.IsAny&lt;ClaimsPrincipal&gt;(), ...)).Returns(true).Verifiable();

var controller = new MyController(...);

var mockHttpContext = new Mock&lt;HttpContext&gt;();
mockHttpContext.Setup(m =&gt; m.User).Returns(mockPrincipal.Object);

controller.ControllerContext = new ControllerContext();
controller.ControllerContext.HttpContext = new DefaultHttpContext()
{
 User = mockPrincipal.Object
};

var result = controller.Get() as OkObjectResult;
//Assert results

mockAuthHandler.Verify();
</code></pre>

blocks|key|1902279|text|我想直接命中我的控制器，只需要像AutoFac一样使用DI。为此，我首先注册ContextController。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1902280|var+identity+=+new+GenericIdentity("Test+User");
var+httpContext+=+new+DefaultHttpContext()
{
++++User+=+new+GenericPrincipal(identity,+null)
};

var+context+=+new+ControllerContext+{+HttpContext+=+httpContext};
builder.RegisterInstance(context);|code-block|syntax|javascript|1902281|接下来，我在注册控制器时启用属性注入。|1902282|++builder.RegisterAssemblyTypes(assembly)
++++++++++++++++++++.Where(t+=>+t.Name.EndsWith("Controller")).PropertiesAutowired();|1902283|然后填充User.Identity.Name，在调用Controller上的方法时，我不需要做任何特殊的事情。|1902284|public+async+Task<ActionResult<IEnumerable<Employee>>>+Get()
{
++++var+requestedBy+=+User.Identity?.Name;
++++..................|1902285|entityMap^0|12|H|0|0|0|0|4|I|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|H|7|13|8|@]|D|@]|E|$I|J]]|$1|S|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|T|$]]

I want to hit my Controllers directly and just use DI like AutoFac. To do this I first registering <code>ContextController</code>.
<pre><code>var identity = new GenericIdentity(&quot;Test User&quot;);
var httpContext = new DefaultHttpContext()
{
 User = new GenericPrincipal(identity, null)
};

var context = new ControllerContext { HttpContext = httpContext};
builder.RegisterInstance(context);
</code></pre>
Next I enable property injection when I register the Controllers.
<pre><code> builder.RegisterAssemblyTypes(assembly)
 .Where(t =&gt; t.Name.EndsWith(&quot;Controller&quot;)).PropertiesAutowired();
</code></pre>
Then <code>User.Identity.Name</code> is populated, and I do not need to do anything special when calling a method on my Controller.
<pre><code>public async Task&lt;ActionResult&lt;IEnumerable&lt;Employee&gt;&gt;&gt; Get()
{
 var requestedBy = User.Identity?.Name;
 ..................
</code></pre>

blocks|key|1902312|text|我得到了一个brownfield+.net+4.8项目，我需要将其转换为.net+5.0，并且我希望保留尽可能多的原始代码，包括单元/集成测试。控制器的测试在很大程度上依赖于上下文，因此我创建了这个扩展方法来启用设置令牌、声明和标题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1902313|public+static+void+AddContextMock(
++++this+ControllerBase+controller,
++++IEnumerable<(string+key,+string+value)>+claims+=+null,
++++IEnumerable<(string+key,+string+value)>+tokens+=+null,
++++IEnumerable<(string+key,+string+value)>+headers+=+null)
{
++++HttpContext+mockContext+=+new+DefaultHttpContext();
++++if(claims+!=+null)
++++{
++++++++mockContext.User+=+SetupClaims(claims);
++++}
++++if(tokens+!=+null)
++++{
++++++++mockContext.RequestServices+=+SetupTokens(tokens);
++++}
++++if(headers+!=+null)
++++{
++++++++SetupHeaders(mockContext,+headers);
++++}

++++controller.ControllerContext+=+new+ControllerContext()
++++{
++++++++HttpContext+=+mockContext
++++};
}

private+static+void+SetupHeaders(HttpContext+mockContext,+IEnumerable<(string+key,+string+value)>+headers)
{
++++foreach(var+header+in+headers)
++++{
++++++++mockContext.Request.Headers.Add(header.key,+header.value);
++++}
}

private+static+ClaimsPrincipal+SetupClaims(IEnumerable<(string+key,+string+value)>+claimValues)
{
++++var+claims+=+claimValues.Select(c+=>+new+Claim(c.key,+c.value));
++++return+new+ClaimsPrincipal(new+ClaimsIdentity(claims,+"mock"));
}

private+static+IServiceProvider+SetupTokens(IEnumerable<(string+key,+string+value)>+tokenValues)
{
++++var+mockServiceProvider+=+new+Mock<IServiceProvider>();
++++var+authenticationServiceMock+=+new+Mock<IAuthenticationService>();
++++var+authResult+=+AuthenticateResult.Success(
++++++++new+AuthenticationTicket(new+ClaimsPrincipal(),+null));
++++var+tokens+=+tokenValues.Select(t+=>+new+AuthenticationToken+{+Name+=+t.key,+Value+=+t.value+});
++++authResult.Properties.StoreTokens(tokens);

++++authenticationServiceMock
++++++++.Setup(x+=>+x.AuthenticateAsync(It.IsAny<HttpContext>(),+null))
++++++++.ReturnsAsync(authResult);

++++mockServiceProvider.Setup(_+=>+_.GetService(typeof(IAuthenticationService))).Returns(authenticationServiceMock.Object);
++++return+mockServiceProvider.Object;
}|code-block|syntax|javascript|1902314|这使用了Moq，但是可以适应其他的模拟框架。由于我依赖于默认身份验证，所以身份验证类型被硬编码为“模拟”，但这也可以提供。|1902315|其用途如下：|1902316|_controllerUnderTest.AddContextMock(
++++claims:+new[]
++++{
++++++++(ClaimTypes.Name,+"UserName"),
++++++++(ClaimTypes.MobilePhone,+"1234"),
++++},
++++tokens:+new[]+
++++{+
++++++++("access_token",+"accessTokenValue")+
++++},
++++headers:+new[]
++++{
++++++++("header",+"headerValue")
++++});|1902317|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|S|8|@]|9|@]|A|$E|F]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I got a brownfield .net 4.8 project that I needed to convert to .net 5.0 and I wanted to keep as much of the original code as possible, including the unit-/integration tests. The test for Controllers relied on the Context a lot so I created this Extension method to enable setting tokens, claims and headers:
<pre class="lang-cs prettyprint-override"><code>public static void AddContextMock(
 this ControllerBase controller,
 IEnumerable&lt;(string key, string value)&gt; claims = null,
 IEnumerable&lt;(string key, string value)&gt; tokens = null,
 IEnumerable&lt;(string key, string value)&gt; headers = null)
{
 HttpContext mockContext = new DefaultHttpContext();
 if(claims != null)
 {
 mockContext.User = SetupClaims(claims);
 }
 if(tokens != null)
 {
 mockContext.RequestServices = SetupTokens(tokens);
 }
 if(headers != null)
 {
 SetupHeaders(mockContext, headers);
 }

 controller.ControllerContext = new ControllerContext()
 {
 HttpContext = mockContext
 };
}

private static void SetupHeaders(HttpContext mockContext, IEnumerable&lt;(string key, string value)&gt; headers)
{
 foreach(var header in headers)
 {
 mockContext.Request.Headers.Add(header.key, header.value);
 }
}

private static ClaimsPrincipal SetupClaims(IEnumerable&lt;(string key, string value)&gt; claimValues)
{
 var claims = claimValues.Select(c =&gt; new Claim(c.key, c.value));
 return new ClaimsPrincipal(new ClaimsIdentity(claims, &quot;mock&quot;));
}

private static IServiceProvider SetupTokens(IEnumerable&lt;(string key, string value)&gt; tokenValues)
{
 var mockServiceProvider = new Mock&lt;IServiceProvider&gt;();
 var authenticationServiceMock = new Mock&lt;IAuthenticationService&gt;();
 var authResult = AuthenticateResult.Success(
 new AuthenticationTicket(new ClaimsPrincipal(), null));
 var tokens = tokenValues.Select(t =&gt; new AuthenticationToken { Name = t.key, Value = t.value });
 authResult.Properties.StoreTokens(tokens);

 authenticationServiceMock
 .Setup(x =&gt; x.AuthenticateAsync(It.IsAny&lt;HttpContext&gt;(), null))
 .ReturnsAsync(authResult);

 mockServiceProvider.Setup(_ =&gt; _.GetService(typeof(IAuthenticationService))).Returns(authenticationServiceMock.Object);
 return mockServiceProvider.Object;
}
</code></pre>
This uses Moq but can be adapted to other mocking frameworks. The authentication type is hardcoded to &quot;mock&quot; since I rely on default authentication but this could be supplied as well.
It is used as such:
<pre class="lang-cs prettyprint-override"><code>_controllerUnderTest.AddContextMock(
 claims: new[]
 {
 (ClaimTypes.Name, &quot;UserName&quot;),
 (ClaimTypes.MobilePhone, &quot;1234&quot;),
 },
 tokens: new[] 
 { 
 (&quot;access_token&quot;, &quot;accessTokenValue&quot;) 
 },
 headers: new[]
 {
 (&quot;header&quot;, &quot;headerValue&quot;)
 });
</code></pre>

blocks|key|1902353|text|如果您正在使用Razor页面，并且想要覆盖这些声明：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1902354|[SetUp]
public+void+Setup()
{
++++var+user+=+new+ClaimsPrincipal(new+ClaimsIdentity(
++++new+Claim[]+{+
++++++++new("dateofbirth",+"2000-10-10"),
++++++++new("surname",+"Smith")+},
++++"mock"));

++++_razorModel+=+new+RazorModel()
++++{
++++++++PageContext+=+new+PageContext
++++++++{
++++++++++++HttpContext+=+new+DefaultHttpContext()+{+User+=+user+}
++++++++}
++++};
}|code-block|syntax|javascript|1902355|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

If you're using Razor pages and want to override the claims:
<pre class="lang-cs prettyprint-override"><code>[SetUp]
public void Setup()
{
 var user = new ClaimsPrincipal(new ClaimsIdentity(
 new Claim[] { 
 new(&quot;dateofbirth&quot;, &quot;2000-10-10&quot;),
 new(&quot;surname&quot;, &quot;Smith&quot;) },
 &quot;mock&quot;));

 _razorModel = new RazorModel()
 {
 PageContext = new PageContext
 {
 HttpContext = new DefaultHttpContext() { User = user }
 }
 };
}
</code></pre>

I have an ASP.NET MVC Core application that I am writing unit tests for. One of the action methods uses User name for some functionality:

<pre><code>SettingsViewModel svm = _context.MySettings(User.Identity.Name);
</code></pre>

which obviously fails in the unit test. I looked around and all suggestions are from .NET 4.5 to mock HttpContext. I am sure there is a better way to do that. I tried to inject IPrincipal, but it threw an error; and I even tried this (out of desperation, I suppose):

<pre><code>public IActionResult Index(IPrincipal principal = null) {
 IPrincipal user = principal ?? User;
 SettingsViewModel svm = _context.MySettings(user.Identity.Name);
 return View(svm);
}
</code></pre>

but this threw an error as well.
Couldn't find anything in the docs either...

Mocking IPrincipal in ASP.NET Core

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个ASP.NET MVC核心应用程序，我正在为它编写单元测试。其中一种操作方法将用户名用于某些功能：SettingsViewModel svm = _context.MySettings(User.Identity.Name);显然在单元测试中失败了。我环顾四周，所有的建议都是从.NET 4.5到模拟HttpCo...

问在IPrincipal内核中模拟ASP.NET
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在IPrincipal内核中模拟ASP.NETEN