blocks|key|1786531|text|我们使用MbUnit和Rihno+Mocks，事实证明它们在一起工作得很好。在进行测试时，您几乎肯定需要进行某种形式的依赖注入，虽然这可以手动完成，但值得看看Castle+Windsor这样的IoC容器。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1786532|看一下约翰·保罗·博德胡德的屏幕投射是非常值得的，让你开始吧。JPB's+Blog|1786533|entityMap|0|LINK|mutability|MUTABLE|url|http://www.mbunit.com/|1|http://www.ayende.com/Blog/archive/2007/03/28/Rhino-Mocks-3.0-Released.aspx|2|http://www.castleproject.org/projects/windsor/|3|http://www.jpboodhoo.com/^0|4|6|0|B|B|1|27|E|2|0|V|A|3|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]|$A|X|B|Y|1|Z]|$A|10|B|11|1|12]]|C|$]]|$1|D|3|E|5|6|7|13|8|@]|9|@$A|14|B|15|1|16]]|C|$]]|$1|F|3|-4|5|6|7|17|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|Q]]|R|$5|I|J|K|C|$L|S]]]]

We use <a href="http://www.mbunit.com/" rel="noreferrer">MbUnit</a> and <a href="http://www.ayende.com/Blog/archive/2007/03/28/Rhino-Mocks-3.0-Released.aspx" rel="noreferrer">Rihno Mocks</a> and they prove to work very well together. When doing TDD you will almost certainly need to do some form of dependency injection, while this can be done manually, its worth looking at an IoC container such as <a href="http://www.castleproject.org/projects/windsor/" rel="noreferrer">Castle Windsor</a>.

It well worth looking at John Paul Bodhood's screen casts to get you started. <a href="http://www.jpboodhoo.com/" rel="noreferrer">JPB's Blog</a>

blocks|key|1786653|text|NUnit和Rhino很适合，auto-mocking+container可能会感兴趣。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1786654|如果您也在考虑BDD，那么NBehave可能是一个不错的选择。然而，如果你只是指与单元测试(xSpec)相关的BDD风格，虽然你可以添加一个框架(尽管像specunit这样的东西确实添加了一些语法糖)，但你可能想看看MSpec也很有趣。|1786655|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ayende.com/Blog/archive/2007/06/08/The-Auto-Mocking-Container.aspx|1|http://nbehave.org/|2|http://code.google.com/p/specunit-net/|3|http://codebetter.com/blogs/aaron.jensen/archive/2008/05/08/introducing-machine-specifications-or-mspec-for-short.aspx^0|F|M|0|0|D|7|1|24|8|2|30|5|3|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|@$A|Y|B|Z|1|10]|$A|11|B|12|1|13]|$A|14|B|15|1|16]]|C|$]]|$1|F|3|-4|5|6|7|17|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|Q]]|R|$5|I|J|K|C|$L|S]]]]

NUnit and Rhino suit well and the <a href="http://www.ayende.com/Blog/archive/2007/06/08/The-Auto-Mocking-Container.aspx" rel="noreferrer">auto-mocking container</a> might be of interest.

If you're looking at BDD too then <a href="http://nbehave.org/" rel="noreferrer">NBehave</a> is probably a good choice. If however you just mean the style of BDD that relates to unit testing (xSpec) though you can get away with adding a framework (though things like <a href="http://code.google.com/p/specunit-net/" rel="noreferrer">specunit</a> do add some synctactic sugar), but you might want to look at <a href="http://codebetter.com/blogs/aaron.jensen/archive/2008/05/08/introducing-machine-specifications-or-mspec-for-short.aspx" rel="noreferrer">MSpec</a> is also interesting.

blocks|key|1571918|text|查看Rob+Conery关于使用MSpec的BDD的截屏视频。令人印象深刻的http://blog.wekeroad.com/mvc-storefront/kona-3/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1571919|编辑:我现在使用这种方法：http://10printhello.com/the-one-bdd-framework-to-rule-them/|1571920|entityMap|0|LINK|mutability|MUTABLE|url|http://blog.wekeroad.com/mvc-storefront/kona-3/|1|http://10printhello.com/the-one-bdd-framework-to-rule-them/^0|12|1B|0|0|D|1N|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

Check out Rob Conery's screencast on BDD using MSpec. Very impressive <a href="http://blog.wekeroad.com/mvc-storefront/kona-3/" rel="nofollow noreferrer">http://blog.wekeroad.com/mvc-storefront/kona-3/</a>

edit: I now use this approach: <a href="http://10printhello.com/the-one-bdd-framework-to-rule-them/" rel="nofollow noreferrer">http://10printhello.com/the-one-bdd-framework-to-rule-them/</a>

blocks|key|1786384|text|对于模拟对象库，我发现BSD许可的Rhino.Mocks是相当令人满意的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1786385|entityMap|0|LINK|mutability|MUTABLE|url|http://ayende.com/projects/rhino-mocks.aspx^0|H|B|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]]]]

For a Mock Object library, I've found the BSD-licensed <a href="http://ayende.com/projects/rhino-mocks.aspx" rel="nofollow noreferrer">Rhino.Mocks</a> to be rather pleasing.

blocks|key|1571526|text|我使用NUnit也取得了巨大的成功。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1571527|当需要模拟对象时，我也会使用NMock。额外的好处是，创建模拟对象的工厂称为Mockery。|1571528|为了方便单元测试的运行，我在编写代码时使用了TestDriven.NET来运行单元测试。此外，我还使用了Cruise+Control+.NET来监视SVN，并检查每个新提交的内容是否构建并通过了所有单元测试。|1571529|entityMap|0|LINK|mutability|MUTABLE|url|http://www.nunit.org/|1|http://www.nmock.org/|2|http://testdriven.net/|3|http://ccnet.thoughtworks.com/^0|3|5|0|0|E|5|1|0|M|E|2|1G|J|3|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|D|3|E|5|6|7|Z|8|@]|9|@$A|10|B|11|1|12]]|C|$]]|$1|F|3|G|5|6|7|13|8|@]|9|@$A|14|B|15|1|16]|$A|17|B|18|1|19]]|C|$]]|$1|H|3|-4|5|6|7|1A|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]|R|$5|K|L|M|C|$N|S]]|T|$5|K|L|M|C|$N|U]]]]

I've had great success using <a href="http://www.nunit.org" rel="nofollow noreferrer">NUnit</a> as well.

I've also used <a href="http://www.nmock.org" rel="nofollow noreferrer">NMock</a> when the need arose for mock objects. As an added bonus, the factory for creating your mock objects is called the Mockery.

To facilitate the running of unit tests, I've used <a href="http://testdriven.net" rel="nofollow noreferrer">TestDriven.NET</a> to run unit tests as I coded. Also, I've used <a href="http://ccnet.thoughtworks.com" rel="nofollow noreferrer">Cruise Control .NET</a> to watch SVN and check that every new commit builds and passes all unit tests.

blocks|key|1571873|text|这可能是对已经说过的内容的总结，但我个人使用Rhino+Mock和MBUnit进行测试。Rhino+Mocks是一个免费且开源的模拟框架。Rhino+Mock的优点是我们不需要像在NMock中那样使用魔法字符串来设置您的期望。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1571874|我喜欢MBUnit，因为MbUnit有RowTests的概念，它允许你改变你的测试方法的输入。MBUnit也是免费的。|1571875|您还希望确保您的CI+(持续集成服务器)支持您为单元测试框架选择的任何内容。默认情况下，巡航Control.NET支持Nunit，您必须做一些额外的工作才能让MBUnit在ccnet中工作。|1571876|从集成开发环境的角度来看，你必须有TestDriven.NET。TestDriven.NET允许你在集成开发环境中右击并运行测试，它支持MBUnit和Nunit等。|1571877|NBehave是我使用的BDD库。我没有使用任何其他的工具，所以我不能将它们与您进行比较，但是MBUnit团队的Gallio支持NBehave，这意味着您可以像使用TestDriven.NET进行单元测试一样运行您的BDD测试。|1571878|我也强烈推荐Resharper。您会发现使用此重构和指导工具，您的工作效率将显著提高。它将帮助您在开发测试时更改代码。|1571879|希望这能有所帮助|1571880|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

This is probably a summary of what has already been said, but for TDD I personally use Rhino Mocks and MBUnit. Rhino Mocks is a mocking framework that is free and open source. The advantage of Rhino Mocks is we do not need to use magic strings in setting your expectations as you do in NMock. 

I like MBUnit because MbUnit has the concept of RowTests which allow you to vary your inputs to your test method. MBUnit is also freely available.

You also want to make sure that whatever you choose for your unit testing framework is supported by your CI (Continuous Integration Server). Nunit is supported by default in Cruise Control.NET and you have to do a little extra work to get MBUnit to work in ccnet.

From an IDE standpoint you must have TestDriven.NET. TestDriven.NET allows you to right click and run tests in the IDE and it supports MBUnit and Nunit and others.

NBehave is the BDD library I have used. I have not used any others so I could not compare and contrast them with you, but NBehave is supported by Gallio from the MBUnit team, which means you can run your BDD tests just as you would your unit tests with TestDriven.NET.

I would also highly recommend Resharper. You will find your productivity increase significantly with this refactoring and guidance tool. It will assist you with changing your code as you are developing your tests.

Hope this helps

blocks|key|1571705|text|在TFS中使用nUnit并不太难。在codeplex上甚至有一个项目可以实现这一点：NUnit+for+Team+Build，它甚至将结果“发布”到仓库中。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1571706|我还没有尝试过它--但是我建议那些在nUnit上有大量投资(或者对它有强烈的偏好，而不是对MSTest工具感兴趣)的客户继续使用nUnit，而不是尝试转换所有现有的测试。|1571707|entityMap|0|LINK|mutability|MUTABLE|url|http://www.codeplex.com/nunit4teambuild^0|16|K|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]]]]

Using nUnit with TFS isn't too difficult. There's even a project on codeplex to implement this: <a href="http://www.codeplex.com/nunit4teambuild" rel="nofollow noreferrer">NUnit for Team Build</a> which even "publishes" the results to the warehouse.

I haven't tried it - but I would advise clients who have a large investment (or who have a strong preference for it over the MSTest tool) in nUnit who are interested in implementing TFS to continue with nUnit as opposed to trying convert all their existing tests.

blocks|key|1786729|text|我必须为Moq做一个大喊。它是一个干净轻便的模仿框架，引导你进入成功的深渊。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1786730|内置到TFS中的测试工具是正常的。他们会完成工作，但与他们一起工作通常会有点麻烦。生成的报告、代码覆盖率和一些其他部分尤其糟糕。他们会让你在22岁而不是50岁时变成光头。|1786731|如果你真的喜欢测试，可以考虑尝试一些持续集成。你会很快感受到回归带来的痛苦，这种痛苦可能会帮助你更快地到达最终目标。|1786732|不管你做什么，尝试一些，看看哪一个是最自然的，如果你有时间的话。祝你好运，祝你编码愉快。|1786733|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/p/moq/^0|4|3|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]]]

I have to put a shout-out for <a href="http://code.google.com/p/moq/" rel="nofollow noreferrer" title="This is the project site, check it out">Moq</a>. It is a clean light mocking framework that guides you into the pit of success.
The testing tools built into TFS are okay. They will get the job done but can often be a little cumbersome to work with. The generated reports, code coverage and a few other portions are particularly bad. They make you go bald at 22 rather than 50.
If you are really loving the testing, consider trying some Continuous Integration. You will feel the pain from regression quickly and this pain potentially helps you get to the end goal faster.
Regardless of what you do, try out a few and see which one is the most natural, if you have time. Good luck and happy coding.

blocks|key|1786309|text|NUnit一直是我的最爱。但是，如果您使用TFS作为源代码控制，我建议您继续使用Microsoft+Stack。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1786310|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

NUnit is always a favorite of mine. However if you are using TFS as your source control I suggest you stick with the Microsoft Stack.

blocks|key|1571964|text|在我的项目中，我成功地使用了NUnit和TestDriven.NET。您可以创建一个单独的库来托管测试代码，也可以将其放入可执行文件或库中。这完全取决于您是否希望您的生产代码与测试代码交织在一起。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1571965|对于依赖注入，我在当前的项目中使用了NInject，它工作得很好。如果你使用构造函数注入，你不需要用Inject属性弄乱你的代码。|offset|length|1571966|我还没有在我的.NET+2.0项目中使用模拟库，但是对于另一个.NET+3.5项目，我将使用Moq。|1571967|请注意，所有这些都适用于.NET+2.0及更高版本。(Moq除外)|1571968|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ninject.org/|1|http://code.google.com/p/moq/^0|0|I|7|0|0|1A|3|1|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@$D|V|E|W|1|X]]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@$D|Z|E|10|1|11]]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]|R|$5|M|N|O|A|$P|S]]]]

For my project, I used NUnit and TestDriven.NET with great success. You can either create a separate library just to host your test code or put it in your executable or library. It all depends on whether you want your production code to be intertwined with your test code.
For Dependency Injection, I use <a href="http://www.ninject.org/" rel="nofollow noreferrer" title="NInject">NInject</a> in my current project and it works great. If you use Constructor injection, you don't need to clutter your code with the [Inject] attribute.
I haven't used a mock library for my .NET 2.0 project but for another .NET 3.5 project I will use <a href="http://code.google.com/p/moq/" rel="nofollow noreferrer" title="Moq">Moq</a>.
Note that all these work with .NET 2.0 and higher. (except Moq)

I'm looking to add a testing suite to my application, however I can't move to the newer testing frameworks for .NET 3.5. 

Does anyone have a suggestion about good testing frameworks to use?

What's the best way to implement BDD/TDD in .NET 2.0?

我希望在我的应用程序中添加一个测试套件，但是我不能转移到.NET 3.5的较新测试框架。有没有人对使用好的测试框架有什么建议？

问在.NET 2.0中实现BDD/TDD的最佳方式是什么？
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在.NET 2.0中实现BDD/TDD的最佳方式是什么？EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在.NET 2.0中实现BDD/TDD的最佳方式是什么？
EN