对于 C# 应用程序来说，哪些 BDD 工具更合适并且更有优势？
我想知道您推荐哪种工具在 BDD 开发过程中更有优势：
我个人使用 Cucumber（在 Ruby for Windows 上），而且看起来 SpecFlow 非常相似。 但我希望您推荐任何其他好工具！
I would like to know your recommendation for which tool has more advantages when it comes to BDD development process:
I personally use Cucumber (on Ruby for Windows), also it seems SpecFlow is very similar.
But I would like your recommendation on any other nice tools!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您可以将 MSpec 添加到您的列表中。 MSpec 是我个人最喜欢的，因为我更经常/经常使用它。与单元测试框架一样，您选择哪一个主要取决于个人喜好。
取出其中几个进行测试运行，然后根据以下因素做出决定：
You could add MSpec to your list. MSpec is my personal favourite simply because I've used it more often/regularly. Which one you chose is, as with Unit Testing frameworks, mainly an primarily a matter of taste.
Take a couple of them out for a test run and decide based on:
您错过了我的建议：
用代码编写。
构建一些可以支持 BDD 的 DSL 并不难。 这是我之前制作的一个。商务人士可以阅读此内容。
实际上，使用 BDD 框架的唯一原因是捕获您与业务利益相关者之间的对话。这些对话更重要！如果您的业务利益相关者本身没有阅读或编写场景，那么您使用 BDD 框架所做的就是引入另一层间接层。 （我帮助编写了 JBehave，但仍然更喜欢代码。）
话虽如此，如果您觉得自己从 BDD 框架中受益，我听说 SpecFlow 很棒。
You've missed out my recommendation:
Write it in code.
It's not very hard to knock up a little DSL which can support your BDD. Here's one I made earlier. Even business people can read this.
The only reason to use BDD frameworks, really, is to capture the conversations you have with your business stakeholders. The conversations are much more important! If your business stakeholders aren't reading or writing the scenarios themselves then all you do with a BDD framework is introduce another layer of indirection. (I helped write JBehave and still prefer code.)
Having said that, if you feel you get benefit from a BDD framework, I hear great things about SpecFlow.