通过示例进行规范的工具建议，其中分析师（而不是开发人员）编写测试？
受到 Gojko Adzic 的示例规范的启发，我们希望发起一种 bdd 风格的方法。实现是用 java 实现的，开发人员已经在编写 junit 测试。
关键要求是规范（验收测试）可以由非开发人员编写、阅读和维护。该项目将作为一个敏捷团队运行 - 因此，如果开发人员必须检测规范，那就没问题了。但是，我不希望开发人员、测试人员或领域专家必须阅读或编写看起来像代码的东西。
到目前为止，我已经查看了 FitNesse、Concordion 和其他各种（例如 Spock）。我拒绝了 spock 和类似的工具，因为它们的主要受众是开发人员。 FitNesse 似乎可以满足大部分要求。
然而，Concordion 可能是目前最受欢迎的：规格看起来更干净、更简单。
所以我的问题（实际上是三个）：
- 对于我应该考虑的其他工具有什么建议吗？
- 有没有人以这种方式成功地使用协奏曲（或其他工具）？
- 协和仍然在积极开发/支持吗？从网站上很难看出，大多数相关的 SO 问题都有好几年的历史了。
谢谢。
We are looking to initiate a bdd-style approach, inspired by Gojko Adzic's specification by example. Implementation is in java and devs are already writing junit tests.
Key requirement is that specifications (acceptance tests) can be written, read and maintained by non-developers. The project will run as an agile team - so it's fine if devs have to instrument the specs. However, I don't want developers, testers or domain experts having to read or write something that looks like code.
So far I've looked at FitNesse, Concordion and various others (e.g. Spock). I've rejected spock and similar tools because they target developers as the primary audience. FitNesse seems to meet most of the requirements.
Concordion is probably current favourite however: specs looks cleaner and simpler.
So my question (actually three):
- Any suggestions for other tools I should look at?
- Has anyone been successful with using concordion (or another tool) in this way?
- Is concordion still actively developed/supported? Difficult to tell from website and most related SO questions are several years old.
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我曾与许多团队合作，使用 Concordion 实施实例化需求说明。我们训练整个团队用 HTML 编写 Concordion 规范。只需要一小部分 HTML，因此我们可以在大约 30 分钟内培训新手。通常，我们让测试人员编写 HTML 规范，有时由 BA 或 Scrum Master 来编写。
我们使用 Eclipse（网页编辑器）来编辑 HTML。这很有效，只是 Concordion 需要有效的 XHTML，而 Eclipse 不允许将 HTML 验证为 XHTML。这主要显示为
使用标签而不是
。我们在训练中解决了这个问题。我们还对整个团队进行源代码控制使用方面的培训。通过使用 Eclipse，我们拥有一个用于编辑和源代码控制的用户界面。我们还发现，让团队使用相同的 IDE 是迈向跨职能团队的一步。
我知道另一个团队的 BA 正在使用基于 Mac 的 HTML 编辑器编写规范。
Concordion 得到积极维护，在邮件列表（Yahoo）和问题列表上有快速响应。 Concordion 代码库很稳定。过去一年左右的积极开发主要集中在扩展机制上，允许用户添加命令和侦听器（例如，用于捕获测试失败的屏幕截图）。
I've worked with a number of teams implementing Specification by Example with Concordion. We train our whole team up to write Concordion specifications in HTML. Only a small subset of HTML is required, so we can train a newbie in about 30 minutes. Typically we have the testers writing the HTML specification, with the BA or Scrum Master sometimes writing them.
We've used Eclipse (Web Page Editor) for editing the HTML. This works well, except that Concordion requires valid XHTML, and Eclipse does not allow HTML to be validated as XHTML. This mostly shows with <br> tags being used rather than <br/>. We cover this off in training. We also train the whole team in the use of source control. By using Eclipse, we have a single user interface for editing and source control. We also find that having the team using the same IDE is a step on the journey to a cross-functional team.
I know of another team where the BA is writing the specifications using a Mac-based HTML editor.
Concordion is actively maintained, with rapid responses on the mailing list (Yahoo) and the issues list. The Concordion codebase is stable. The active development over the last year or so has focussed on the extension mechanism, allowing users to add commands and listeners (eg. for capturing screenshots on test failure).
另请查看 Cucumber 和 JBehave，它们都允许以纯文本形式编写规范。
如果您选择使用 FitNesse，那么 Slim 也值得一看，它位于 FitNesse 后面，取代了 Fit。它提供的表格格式与 Fit 略有不同，我发现它更适合 BDD。
Also take a look at Cucumber and JBehave, both of which allow specifications to be written in plain text.
If you choose to use FitNesse, it may also be worth looking at Slim, which sits behind FitNesse in place of Fit. It provides slightly different table formats to Fit, and I've found it suits BDD much better.
只是为了更新主题，您还可以考虑 jnario。
Just to update the topic, you can also consider jnario.