SBE规范应如何完善？ [英] how complete should SBE specifications be?

问题描述

我正在开发一个相当大的现有代码库，在该代码库中创建了SBE规范来定义产品的行为。

I'm working on a fairly large existing code base where SBE specifications are created to define the behavior of the product.

当前大约有450种情况，并且

There are currently around 450 scenarios, and this number is growing with each new feature added to the code base.

与传统的单行要求语句相比，很难从高层次上了解该功能。该系统由于SBE规范的冗长性质。例如，这些故事目前总共有46,830个单词：

Compared to traditional one line requirement statements, it is difficult to get a high level understanding of the functionality of the system due to wordy nature of the SBE specifications. As an example, the stories currently have a total of 46,830 words:

$ find src/main/resources/stories/ -name *.story | xargs cat | wc -w
   46830

另一个问题是我们正在使用 gerrit代码审查工具，用于协作处理故事，从而导致团队之间的正式沟通。

One other issue is that we are using gerrit code review tool for collaborating on stories, which is resulting in formalized communication between the team.

问题1 ：SBE是否应该是一个完整而全面的回归测试套件（示例）？还是应该只关注每个冲刺所需的关键功能？

Question 1: Should the SBE's be a complete and comprehensive regression test suite (example)? Or, should they only focus on the key functionality required in each sprint?

问题2 ：如答案此处，是诸如问题跟踪程序之类的工具为大型项目管理故事？

Question 2: As mentioned on the answer here, are tools such as issue trackers required to manage stories for large projects?

推荐答案

通常，验收测试和行为测试的重点在于确保价值的传递，因为其本身就是本性他们是黑盒测试的一种形式。

Normally acceptance tests and behavior tests focus on making sure value is delivered because by their own nature they are a form of black box testing.

所以对于1.答案是否定的，它们不应该完整。他们应该确保产生价值的外部行为不会消退。

So for 1. the answer is NO, they should not be complete. They should make sure that the external behaviors that produce value do not regress.

关于2。我会避免使用此类工具，因为很难以时间为基础查询它们信息：通常，诸如Rally或Version 1之类的敏捷工具都可以制作燃尽图，以按日和速度图表显示燃尽情况。使用错误跟踪器跟踪和使用敏捷工具进行敏捷！

Regarding 2. I would avoid such tools, because they are devilishly hard to query to get time based information: typically agile tools like Rally or Version one are able to do burn down charts to give you burn downs by day and velocity charts. Use bug trackers for tracks and agile tools for agile!

这篇关于SBE规范应如何完善？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！