blocks|key|684187|text|通常，当您讨论单元测试时，您测试的是一个单独的过程或方法，而不是整个系统，同时试图消除所有外部依赖。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|684188|换句话说，当测试控制器时，你是一个接一个的编写测试方法，你甚至不需要加载视图或模型，这些都是你应该“模拟”出来的部分。然后，您可以更改模拟以返回值或错误，这些值或错误在其他测试中难以重现。|684189|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Usually when you're talking about unit tests, you're testing one individual procedure or method, not an entire system, while trying to eliminate all external dependencies. 

In other words, when testing the controller, you're writing tests method by method and you should not need to even have the view or model loaded, those are the parts you should "mock out". You can then change the mocks to return values or errors that are hard to reproduce in other testing.

blocks|key|468224|text|我看不出对控制器进行单元测试有多大意义，因为它通常只是连接其他部分的一段代码。单元测试通常包括大量的模拟，只是验证其他服务是否正确连接。测试本身是实现代码的反映。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|468225|我更喜欢集成测试--我不是从一个具体的控制器开始，而是从一个Url开始，并验证返回的Model是否具有正确的值。在Ivonna的帮助下，测试可能如下所示：|offset|length|468226|var+response+=+new+TestSession().Get("/Users/List");
Assert.IsInstanceOf<UserListModel>(response.Model);

var+model+=+(UserListModel)+response.Model;
Assert.AreEqual(1,+model.Users.Count);|code-block|syntax|javascript|468227|我可以模拟数据库访问，但我更喜欢一种不同的方法:设置一个内存中的SQLite实例，并在每次新测试中重新创建它，以及所需的数据。它使我的测试足够快，但我没有复杂的模仿，而是让它们变得清晰，例如，只需创建并保存一个用户实例，而不是模仿UserService+(这可能是一个实现细节)。|style|CODE|468228|entityMap|0|LINK|mutability|MUTABLE|url|http://ivonna.biz/^0|0|1L|6|0|0|0|37|B|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@$D|Y|E|Z|1|10]]|A|$]]|$1|F|3|G|5|H|7|11|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|12|8|@$D|13|E|14|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

I don't see much point in unit testing the controller, since it is usually just a piece of code that connects other pieces. Unit testing it typically includes lots of mocking and just verifies that the other services are connected correctly. The test itself is a reflection of the implementing code. 

I prefer integration tests -- I start not with a concrete controller, but with an Url, and verify that the returned Model has the correct values. With the help of <a href="http://ivonna.biz" rel="nofollow">Ivonna</a>, the test might look like:

<pre><code>var response = new TestSession().Get("/Users/List");
Assert.IsInstanceOf&lt;UserListModel&gt;(response.Model);

var model = (UserListModel) response.Model;
Assert.AreEqual(1, model.Users.Count);
</code></pre>

I can mock the database access, but I prefer a different approach: setup an in-memory instance of SQLite, and recreate it with each new test, together with the required data. It makes my tests fast enough, but instead of complicated mocking, I make them clear, e.g. just create and save a User instance, rather than mock the <code>UserService</code> (which might be an implementation detail).

blocks|key|468293|text|你应该首先让你的控制器节食。然后你就可以对它们进行have+fun单元测试了。如果它们很胖，并且您已经将所有的业务逻辑都塞入其中，我同意您将在您的单元测试中到处嘲笑这些东西，并抱怨这是浪费时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|468294|当您谈到复杂的逻辑时，这并不一定意味着此逻辑不能在不同的层中分离，每个方法都要单独进行单元测试。|468295|entityMap|0|LINK|mutability|MUTABLE|url|http://mvccontrib.codeplex.com/wikipage?title=TestHelper^0|P|8|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

You should first put your controllers on a diet. Then you can <a href="http://mvccontrib.codeplex.com/wikipage?title=TestHelper" rel="noreferrer">have fun</a> unit testing them. If they are fat and you have stuffed all your business logic inside them, I agree that you will be passing your life mocking stuff around in your unit tests and complaining that this is a waste of time.

When you talk about complex logic, this doesn't necessarily mean that this logic cannot be separated in different layers and each method be unit tested in isolation.

blocks|key|684346|text|对于ASP.NET+Core，我通常遵循以下指南|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|684347|https://docs.microsoft.com/en-us/aspnet/core/mvc/controllers/testing?view=aspnetcore-5.0|684348|代码示例：|684349|https://github.com/dotnet/AspNetCore.Docs/tree/master/aspnetcore/mvc/controllers/testing/samples/|684350|示例：|684351|控制器：|684352|public+class+HomeController+:+Controller
{
++++private+readonly+IBrainstormSessionRepository+_sessionRepository;

++++public+HomeController(IBrainstormSessionRepository+sessionRepository)
++++{
++++++++_sessionRepository+=+sessionRepository;
++++}

++++public+async+Task<IActionResult>+Index()
++++{
++++++++var+sessionList+=+await+_sessionRepository.ListAsync();

++++++++var+model+=+sessionList.Select(session+=>+new+StormSessionViewModel()
++++++++{
++++++++++++Id+=+session.Id,
++++++++++++DateCreated+=+session.DateCreated,
++++++++++++Name+=+session.Name,
++++++++++++IdeaCount+=+session.Ideas.Count
++++++++});

++++++++return+View(model);
++++}

++++public+class+NewSessionModel
++++{
++++++++[Required]
++++++++public+string+SessionName+{+get;+set;+}
++++}

++++[HttpPost]
++++public+async+Task<IActionResult>+Index(NewSessionModel+model)
++++{
++++++++if+(!ModelState.IsValid)
++++++++{
++++++++++++return+BadRequest(ModelState);
++++++++}
++++++++else
++++++++{
++++++++++++await+_sessionRepository.AddAsync(new+BrainstormSession()
++++++++++++{
++++++++++++++++DateCreated+=+DateTimeOffset.Now,
++++++++++++++++Name+=+model.SessionName
++++++++++++});
++++++++}

++++++++return+RedirectToAction(actionName:+nameof(Index));
++++}
}|code-block|syntax|javascript|684353|单元测试：|684354|[Fact]
public+async+Task+Index_ReturnsAViewResult_WithAListOfBrainstormSessions()
{
++++//+Arrange
++++var+mockRepo+=+new+Mock<IBrainstormSessionRepository>();
++++mockRepo.Setup(repo+=>+repo.ListAsync())
++++++++.ReturnsAsync(GetTestSessions());
++++var+controller+=+new+HomeController(mockRepo.Object);

++++//+Act
++++var+result+=+await+controller.Index();

++++//+Assert
++++var+viewResult+=+Assert.IsType<ViewResult>(result);
++++var+model+=+Assert.IsAssignableFrom<IEnumerable<StormSessionViewModel>>(
++++++++viewResult.ViewData.Model);
++++Assert.Equal(2,+model.Count());
}|684355|entityMap|0|LINK|mutability|MUTABLE|url|1^0|2|C|0|0|2G|0|0|0|0|2P|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|19|8|@]|D|@$9|1A|A|1B|1|1C]]|E|$]]|$1|H|3|I|5|6|7|1D|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|1E|8|@]|D|@$9|1F|A|1G|1|1H]]|E|$]]|$1|L|3|M|5|6|7|1I|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1J|8|@]|D|@]|E|$]]|$1|P|3|Q|5|R|7|1K|8|@]|D|@]|E|$S|T]]|$1|U|3|V|5|6|7|1L|8|@]|D|@]|E|$]]|$1|W|3|X|5|R|7|1M|8|@]|D|@]|E|$S|T]]|$1|Y|3|-4|5|6|7|1N|8|@]|D|@]|E|$]]]|Z|$10|$5|11|12|13|E|$14|G]]|15|$5|11|12|13|E|$14|K]]]]

I usually follow this guide for <code>ASP.NET Core</code>:
<a href="https://docs.microsoft.com/en-us/aspnet/core/mvc/controllers/testing?view=aspnetcore-5.0" rel="nofollow noreferrer">https://docs.microsoft.com/en-us/aspnet/core/mvc/controllers/testing?view=aspnetcore-5.0</a>
Code samples:
<a href="https://github.com/dotnet/AspNetCore.Docs/tree/master/aspnetcore/mvc/controllers/testing/samples/" rel="nofollow noreferrer">https://github.com/dotnet/AspNetCore.Docs/tree/master/aspnetcore/mvc/controllers/testing/samples/</a>
Example:
Controller:
<pre><code>public class HomeController : Controller
{
 private readonly IBrainstormSessionRepository _sessionRepository;

 public HomeController(IBrainstormSessionRepository sessionRepository)
 {
 _sessionRepository = sessionRepository;
 }

 public async Task&lt;IActionResult&gt; Index()
 {
 var sessionList = await _sessionRepository.ListAsync();

 var model = sessionList.Select(session =&gt; new StormSessionViewModel()
 {
 Id = session.Id,
 DateCreated = session.DateCreated,
 Name = session.Name,
 IdeaCount = session.Ideas.Count
 });

 return View(model);
 }

 public class NewSessionModel
 {
 [Required]
 public string SessionName { get; set; }
 }

 [HttpPost]
 public async Task&lt;IActionResult&gt; Index(NewSessionModel model)
 {
 if (!ModelState.IsValid)
 {
 return BadRequest(ModelState);
 }
 else
 {
 await _sessionRepository.AddAsync(new BrainstormSession()
 {
 DateCreated = DateTimeOffset.Now,
 Name = model.SessionName
 });
 }

 return RedirectToAction(actionName: nameof(Index));
 }
}
</code></pre>
Unit test:
<pre><code>[Fact]
public async Task Index_ReturnsAViewResult_WithAListOfBrainstormSessions()
{
 // Arrange
 var mockRepo = new Mock&lt;IBrainstormSessionRepository&gt;();
 mockRepo.Setup(repo =&gt; repo.ListAsync())
 .ReturnsAsync(GetTestSessions());
 var controller = new HomeController(mockRepo.Object);

 // Act
 var result = await controller.Index();

 // Assert
 var viewResult = Assert.IsType&lt;ViewResult&gt;(result);
 var model = Assert.IsAssignableFrom&lt;IEnumerable&lt;StormSessionViewModel&gt;&gt;(
 viewResult.ViewData.Model);
 Assert.Equal(2, model.Count());
}
</code></pre>

I'm looking for advice regarding effective unit testing of .NET mvc controllers. 

Where I work, many such tests use moq to mock the data layer and to assert that certain data-layer methods are called. This doesn't seem useful to me, since it essentially verifies that the implementation has not changed rather than testing the API.

I've also read articles recommending things like checking that the type of view model returned is correct. I can see that providing some value, but alone it doesn't seem to merit the effort of writing many lines of mocking code (our application's data model is very large and complex).

Can anyone suggest some better approaches to controller unit testing or explain why the above approaches are valid/useful?

Thanks!

How should one unit test a .NET MVC controller?

单元测试

集成测试

数据库

SQLite

我正在寻找关于.NET mvc控制器的有效单元测试的建议。在我工作的地方，许多这样的测试都使用moq来模拟数据层，并断言调用了某些数据层方法。这对我来说似乎没有用，因为它本质上是验证实现没有改变，而不是测试API。我也读过一些文章，推荐检查返回的视图模型的类型是否正确。我可以看到它提供了一些价值，但仅凭它似乎不值得编写...

问一个单元应该如何测试一个.NET MVC控制器？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问一个单元应该如何测试一个.NET MVC控制器？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问一个单元应该如何测试一个.NET MVC控制器？
EN