有人用过 Steve Sanderson 的 MvcIntegrationTestFramework 吗？

发布于 2024-07-30 13:03:00 字数 241 浏览 11 评论 0原文

我正在寻找测试 ASP.NET MVC 应用程序的其他方法，并遇到了 Steve Sanderson 的 MvcIntegrationTestFramework. 这种方法看起来很有前途，但我想知道是否有人有任何实际经验可以分享。

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

智商已欠费 2024-08-06 13:03:00

我从中得到了一些非常好的结果。我不在乎这里的其他人怎么说需要测试视图，一旦您将第一行代码添加到视图中，即使代码严格与表示相关，您也会引入潜在的错误，其中编写自动化测试是个好主意。我的主要兴趣是捕获尽可能多的白屏和黄屏异常/错误。为此，我一直在使用 Steven 的介绍性博客文章中的片段来确保页面正确呈现，而不会引发任何异常：

Assert.IsTrue(result.ResponseText.Contains("<!DOCTYPE html"));

我在这个框架中看到的小陷阱可能是：

如果您的网站正在执行一些相当复杂的模型绑定视图和操作方法，您可能会发现自己创建了一些相当大的 NameValueCollections，例如本示例（实际上采用 LogonModel 视图模型对象的操作方法），因为我看不到任何传递任何复杂视图模型对象类型的方法使用此框架进入您的操作方法：

var result =浏览Session.ProcessRequest("/account/logon", HttpVerbs.Post, new NameValueCollection { {"用户名","我的名字"}, {"密码", "我的密码"}, {“returnUrl”，“/home/myActionMethod”} });

执行浏览Session.ProcessRequest("url") 创建一个应用程序主机/上下文，它实际上使用您正在测试的项目中的配置执行您正在测试的Web 代码。这意味着测试运行得有点慢，并且可能会修改真实数据，因为我没有看到一种快速、简单的方法可以使用内置的任何工具将测试中的 Web 项目中的数据访问存储库替换为假版本测试框架。换句话说，您可能需要使用一些基于 web.config 的方法来推出自己的。

I'm having some really good results from it. I don't care what anyone else on here says about the need to test views, as soon as you add your first line of code to a view, even if the code is strictly presentation-related, you introduce a potential for errors for which it would be a good idea to write automated tests. My primary interest is just to catch as many white screen and yellow screen exception/errors as possible. To do so I have been using the snippet from Steven's introductory blog post to ensure that the page rendered properly without throwing any exceptions:

Assert.IsTrue(result.ResponseText.Contains("<!DOCTYPE html"));

The small pitfalls that I see with this framework might be:

If your web site is doing some pretty complex model binding between the views and action methods, you might find yourself creating some pretty large NameValueCollections such as in this example (an action method which actually takes a LogonModel view model object), since I don't see any way of passing any complex view model object types into your action methods by using this framework:

var result = browsingSession.ProcessRequest("/account/logon", HttpVerbs.Post, new NameValueCollection { {"UserName","myName"}, {"Password", "myPassword"}, {"returnUrl", "/home/myActionMethod"} });

Executing browsingSession.ProcessRequest("url") creates an application host/context which actually executes the web code that you are testing using the configuration in the project which you are testing. This means the tests run a bit slowly, and could possibly modify real data, since I don't see a quick and easy way of swapping out your data access repositories in your web project under test with fake versions by using any facility built into this test framework. In other words, you'd probably need to roll your own using some web.config-based means.

回复收藏 0 原文