根据现实世界中的用户请求组织 Cucumber 特征
当我看到有关 Cucumber 的教程时，我会看到“管理用户”等功能示例，其中包含添加用户、删除用户等场景。在启动项目时，这一切都非常好。
但是，我想将关键跟踪器与第三方工具（例如pickler）一起使用，并具有故事功能（关键跟踪器概念），这些功能可以从请求和错误报告中派生（因为它们也可能在其他项目中引用）和代码管理工具）。
我看到的问题是，功能文件的数量可能会变得非常大，因为可以为每个请求启动一个新的文件，而且每个场景的场景数量可能很低，因为它们会分布在不同时期的多个功能文件中，所以你会如何组织它们？
随着时间的推移，测试也会变得太慢，如何减少这种情况？
When I see tutorials regarding cucumber I see feature examples like "manage users" with scenarios such as add users, delete user etc. This all very well when starting a project.
However, I would like to use something like pivotal tracker with third-party tools such as pickler and have features as stories (the pivotal tracker concept) which can be derived from requests and bug reports (as they may be also referred to in other project and code management tools).
The problem I see is that the number of feature files could become quite large because a new one could be started for each request, also the number of scenarios could be low in each because they would be spread over multiple feature files over different periods, so how would you organise them?
also will testing become too slow over time how can this be reduced?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
阅读以下内容：功能！= 故事
Have a read of this: Features != Stories