blocks|key|3747241|text|如果您适当地您的层，单元测试将是可以实现的。正如Rob+Cooper所暗示的，除了管理演示文稿的逻辑之外，不要在WebForm中加入任何逻辑。所有其他的填充、逻辑和持久层应该放在单独的类中，然后您可以单独测试它们。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3747242|为了测试图形用户界面，一些人喜欢selenium。其他人抱怨说，这是一个痛苦的设置。|offset|length|3747243|entityMap|0|LINK|mutability|MUTABLE|url|http://selenium.openqa.org/^0|0|G|8|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

Unit testing will be achievable if you separate your layers appropriately. As Rob Cooper implied, don't put any logic in your WebForm other than logic to manage your presentation. All other stuff logic and persistence layers should be kept in separate classes and then you can test those individually.

To test the GUI some people like <a href="http://selenium.openqa.org/" rel="noreferrer">selenium</a>. Others complain that is a pain to set up.

blocks|key|3747085|text|我将应用程序和至少单元测试从展示器/控制器(您喜欢的mvc/mvp)分层到数据层。这样一来，我就可以很好地覆盖所编写的大部分代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3747086|我已经考虑过FitNesse、Watin和Selenium作为自动化UI测试的选项，但我还没有抽出时间在任何项目中使用它们，所以我们坚持使用人工测试。我倾向于使用FitNesse，但我不能像引入测试驱动开发一样引入它(这会让我很糟糕吗？)我希望不是！)。|3747087|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|$]]

I layer out the application and at least unit test from the presenter/controller (whichever is your preference, mvc/mvp) to the data layer. That way I have good test coverage over most of the code that is written.

I have looked at FitNesse, Watin and Selenium as options to automate the UI testing but I haven't got around to using these on any projects yet, so we stick with human testing. FitNesse was the one I was leaning toward but I couldn't introduce this as well as introducing TDD (does that make me bad? I hope not!).

blocks|key|2902884|text|这是一个很好的问题，我也会订阅的:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2902885|我对web+dev还是比较新的，我也在看很多代码，很大程度上是未经测试的。|2902886|对我来说，我尽可能保持UI+的轻量级()(通常只有几行代码)，并测试其他东西中的垃圾。至少我可以有一些信心，使UI中的所有东西都尽可能地正确。|offset|length|style|BOLD|2902887|它是完美的吗？也许不是，但至少它仍然是高度自动化的，核心代码(大多数“魔法”发生的地方)仍然有相当好的覆盖率。|2902888|entityMap^0|0|0|E|5|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@$F|Q|G|R|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

This is a good question, one that I will be subscribing too :)

I am still relatively new to web dev, and I too am looking at a lot of code that is largely untested.

For me, I keep the UI as light as possible (normally only a few lines of code) and test the crap out of everything else. At least I can then have some confidence that everything that makes it to the UI is as correct as it can be.

Is it perfect? Perhaps not, but at least it as still quite highly automated and the core code (where most of the "magic" happens) still has pretty good coverage..

blocks|key|3747313|text|一种常见的做法是将所有代码移出代码隐藏，并将其放入可以隔离测试的对象中。这类代码通常遵循MVP或MVC设计模式。如果您搜索"Rhino+Igloo“，您可能会找到指向其Subversion存储库的链接。这段代码值得研究，因为它演示了我所见过的Web表单上最好的MVP实现之一。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3747314|当遵循此模式时，您的代码隐藏将做两件事：|3747315|3747316|将所有用户操作转移到演示者提供的presenter.|ordered-list-item|3747317|Render数据。|3747318|3747319|对展示者进行单元测试应该是微不足道的。|3747320|更新:可在此处找到Rhino+Igloo：https://svn.sourceforge.net/svnroot/rhino-tools/trunk/rhino-igloo/|offset|length|3747321|entityMap|0|LINK|mutability|MUTABLE|url|https://svn.sourceforge.net/svnroot/rhino-tools/trunk/rhino-igloo/^0|0|0|0|0|0|0|0|L|1U|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|11|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|12|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|14|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|15|8|@]|9|@$O|16|P|17|1|18]]|A|$]]|$1|Q|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

A common practice is to move all the code you can out of the codebehind and into an object you can test in isolation. Such code will usually follow the MVP or MVC design patterns. If you search on "Rhino Igloo" you will probably find the link to its Subversion repository. That code is worth a study, as it demonstrate one of the best MVP implementations on Web Forms that I have seen.

Your codebehind will, when following this pattern, do two things:

<ol>
<li>Transit all user actions to the presenter.</li>
<li>Render data provided by the presenter.</li>
</ol>

Unit testing the presenter should be trivial.

Update: Rhino Igloo can be found here: <a href="https://svn.sourceforge.net/svnroot/rhino-tools/trunk/rhino-igloo/" rel="nofollow noreferrer">https://svn.sourceforge.net/svnroot/rhino-tools/trunk/rhino-igloo/</a>

blocks|key|709021|text|我通常会避免涉及依赖UI元素的测试。我喜欢集成测试，它测试从数据库层到视图层(但不是实际布局)的所有内容。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|709022|尝试在在新项目中编写一行实际代码之前启动一个测试套件，因为稍后编写测试会更困难。|offset|length|style|BOLD|709023|仔细选择你要测试的东西--不要盲目地为所有东西编写测试。有时这是一项枯燥的任务，所以不要让它变得更难。如果你写了太多的测试，你就有可能在耗时的维护的重压下放弃这项任务。|709024|尝试将尽可能多的功能捆绑到一个测试中。这样，如果出现错误，错误无论如何都会传播。例如，如果您有一个生成摘要的类-测试实际输出，而不是每个辅助函数。|709025|，不要相信自己，。假设你总是会犯错误，所以你写测试是为了让你的生活更容易，而不是更难。|709026|如果你对编写测试感觉不好，那么你可能做错了;)|709027|entityMap^0|0|Q|E|0|0|2C|0|0|21|0|8|Z|0|0|N|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@$D|W|E|X|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|Y|8|@$D|Z|E|10|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|11|8|@$D|12|E|13|F|G]]|9|@]|A|$]]|$1|N|3|O|5|6|7|14|8|@$D|15|E|16|F|G]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|Q|$]]

I would generally avoid testing that involves relying on UI elements. I favor integration testing, which tests everything from your database layer up to the view layer (but not the actual layout). 

Try to start a test suite before writing a line of actual code in a new project, since it's harder to write tests later.

Choose carefully what you test - don't mindlessly write tests for everything. Sometimes it's a boring task, so don't make it harder. If you write too many tests, you risk abandoning that task under the weight of time-consuming maintenance. 

Try to bundle as much functionality as possible into a single test. That way, if something goes wrong, the errors will propagate anyway. For example, if you have a digest-generating class - test the actual output, not every single helper function.

Don't trust yourself. Assume that you will always make mistakes, and so you write tests to make your life easier, not harder.

If you are not feeling good about writing tests, you are probably doing it wrong ;)

blocks|key|2903104|text|已经有人尝试让微软的免费UI自动化(包含在.NET+Framework3.0中)与web应用程序(ASP.NET)一起工作。一家名为Artiso的德国公司恰好写了一篇博客文章，解释了如何实现这一目标(link)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2903105|然而，他们的博客文章也链接了一个MSDN+Webcast，它用winforms解释了UI自动化框架，在我看过这个之后，我注意到你需要AutomationId来获得对相关控件的引用。但是，在web应用程序中，控件没有AutomationId。|2903106|我向Thomas+Schissler+(Artiso)询问了这一点，他解释说这是InternetExplorer的一个主要缺点。他提到了微软(MSAA)的一项较老的技术，并希望IE8能在这方面做得更好。|2903107|然而，我也尝试了一下Watin，它似乎工作得很好。我甚至喜欢Wax，它允许通过Microsoft+Excel工作表实现简单的测试用例。|2903108|entityMap|0|LINK|mutability|MUTABLE|url|http://www.artiso.com/ProBlog/PermaLink,guid,1a01608b-e5fa-4ad9-8c4f-f672a69c3537.aspx|1|http://msdn.microsoft.com/en-us/library/ms971310.aspx^0|2S|4|0|0|0|1Z|4|1|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]|R|$5|M|N|O|C|$P|S]]]]

There have been tries on getting Microsoft's free UI Automation (included in .NET Framework 3.0) to work with web applications (ASP.NET). A german company called Artiso happens to have written a blog entry that explains how to achieve that (<a href="http://www.artiso.com/ProBlog/PermaLink,guid,1a01608b-e5fa-4ad9-8c4f-f672a69c3537.aspx" rel="nofollow noreferrer">link</a>).

However, their blogpost also links an MSDN Webcasts that explains the UI Automation Framework with winforms and after I had a look at this, I noticed you need the AutomationId to get a reference to the respecting controls. However, in web applications, the controls do not have an AutomationId. 

I asked Thomas Schissler (Artiso) about this and he explained that this was a major drawback on InternetExplorer. He referenced an older technology of Microsoft (<a href="http://msdn.microsoft.com/en-us/library/ms971310.aspx" rel="nofollow noreferrer">MSAA</a>) and was hoping himself that IE8 will do this better.

However, I was also giving Watin a try and it seems to work pretty well. I even liked Wax, which allows to implement simple testcases via Microsoft Excel worksheets.

blocks|key|2903159|text|Ivonna可以对视图进行单元测试。我仍然建议将大部分代码转移到其他部分。但是，有些代码就属于这里，比如对控件或控件事件处理程序的引用。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2903160|entityMap|0|LINK|mutability|MUTABLE|url|http://sm-art.biz/Ivonna.aspx^0|0|6|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

<a href="http://sm-art.biz/Ivonna.aspx" rel="nofollow noreferrer">Ivonna</a> can unit test your views. I'd still recommend moving most of the code to other parts. However, some code just belongs there, like references to controls or control event handlers.

Unit testing and ASP.NET web applications are an ambiguous point in my group. More often than not, good testing practices fall through the cracks and web applications end up going live for several years with no tests. 

The cause of this pain point generally revolves around the hassle of writing UI automation mid-development. 

How do you or your organization integrate best TDD practices with web application development?

Best practice for integrating TDD with web application development?

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

单元测试和ASP.NET web应用程序在我的团队中是一个模棱两可的点。通常情况下，好的测试实践失败了，web应用程序最终在没有测试的情况下运行了几年。这个痛点的原因通常是围绕着编写UI自动化开发中期的麻烦。您或您的组织如何将最佳TDD实践与web应用程序开发集成在一起？

问将TDD与web应用程序开发集成的最佳实践？
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将TDD与web应用程序开发集成的最佳实践？EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将TDD与web应用程序开发集成的最佳实践？
EN