带有测试管理器或编码 UI 测试的 BDD
你们中有人有使用 Microsoft 的测试管理器或编码 UI 测试进行真正的 BDD（甚至 TDD）的经验吗？
我对这些工具不是很熟悉，因为我们一直在使用 SpecFlow 和 WatiN 来实现 BDD。 我们组织中的一个团队正在提议测试管理器，但我担心他们错误地认为编写测试的能力实际上是在执行真正的 BDD/TDD，即首先编写一个小测试，然后编写最少的代码来通过测试。
他们向我们展示的示例是在测试管理器中编写一个测试用例，启动 UI 并记录测试的作用。显然，这不是 BDD。真正的 BDD 可以用测试管理器来完成吗？
任何想法表示赞赏。 谢谢， 哇
，快一周了，还没有回复。我是否可以认为这意味着没有人使用 TestManager，因为它是一个 QA 工具而不是开发人员工具？
Do any of you have experience doing true BDD (or even TDD) using Microsoft's Test Manager or Coded UI Tests?
I am not very familiar with these tools as we have been using SpecFlow and WatiN for BDD.
One team in our organization is proposing Test Manager but I fear they are mistaking the ability to write tests with actually doing true BDD/TDD where you write a small test FIRST and THEN write the minimal code to pass the test.
The example they showed us was writing out a test case in Test Manager, firing up the UI and recording what the test does. Obviously, this is NOT BDD. Can true BDD be done with Test Manager?
Any thoughts are appreciated.
Thanks,
Will
Wow, almost a week and no responses. Can I take that to mean that NOBODY uses TestManager because it is a QA tool instead of a developers tool?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
测试管理器和编码 UI 测试更多地用于功能测试。 MTM 中的测试用例不像 Specflow 那样描述功能的行为。我想您可以在测试用例中使用更通用的措辞，以便您可以在编写代码之前编写它们，但这并不是真正由测试用例驱动的。 Specflow 中的 BDD 之所以有效，是因为它为开发人员可以编码的每个步骤生成存根。要自动化 MTM 或 CUIT 中的任何内容，您需要等到开发人员完成后。
也就是说可以一起使用 Specflow 和 CUIT。取决于您如何定义 BDD（开发是由行为规范驱动的吗？），它仍然不是真正的 BDD，也绝对不是 TDD。这些仍然只是术语。他们在一起仍然有价值。如果您对此感兴趣，我写了一篇关于如何让它们一起工作的博客。
http:// rburnham.wordpress.com/2011/03/15/bdd-ui-automation-with-specflow-and-coded-ui-tests/
Test Manager and Coded UI Tests are more for functional tests. A test case in MTM does not describe the behaviour of the feature like specflow does. I guess you could be a little more generic with your wording in the test cases so you can write them before you write the code but this isn't really driven by the test case. BDD in specflow works because it generates stubs for each step which the developer can code against. To automate anything in MTM or CUIT you need to wait until after the developer finishes.
In saying that it is possible to use Specflow and CUIT together. Depending on how you define BDD (is the development driven by the behaviour specs?) its still not really BDD and its defiantly not TDD. Still these are just terms. They still have value together. If you interested in this i wrote a blog on how to get them working together.
http://rburnham.wordpress.com/2011/03/15/bdd-ui-automation-with-specflow-and-coded-ui-tests/
我认为您不能为此使用测试管理器。正如您所指出的，它严重依赖于记录和回放类型的工作流程，这使得它成为不可能。
如果您使用 MTM 的编码 UI 功能（这是完全自动运行带有断言的测试的唯一替代方案），您需要将测试规范“复制”到代码（使用单向生成），因此将很难维持变更。
您可以在任何其他 BDD 工具（例如 SpecFlow）中使用编码 UI 作为 UI 驱动程序来驱动您的应用程序。
I think you cannot use the Test Manager for that. As you have pointed out, it relies heavily on record&playback kind of workflow that makes it impossible.
If you use the Coded UI feature of MTM (which is the only alternative to run tests with assertions full automatically), you need to "duplicate" the test specification to code (with one-way generation), so it will be very hard to maintain the changes.
You can use Coded UI as a UI driver in any other BDD tools (e.g. SpecFlow) however to drive you app.