使用单个 TFS 项目输入 bug 的优点/缺点是什么？
我们正在使用 Team Foundation Server，并且正在尝试确定处理未来错误的最佳方法。我们正在考虑两个选择，但倾向于单一项目。
单一 QA 团队，其中所有错误和测试用例将驻留在 QA 团队拥有的一个 TFS 项目中
所有错误和测试用例都将驻留在与其关联的 TFS 项目中。
有没有人使用单独的单一整体项目来解决错误？ 微软对此提供开箱即用的支持吗？ 举报会受到影响吗？ 我们不想拥有单一项目的原因是什么？
We are using Team Foundation Server and we are trying to decide the best way to handle bug going forward. We are looking at two options but are leaning towards a single project.
Single QA Team where all bugs and test cases will reside in one TFS project owned by the QA team
All bugs and test cases will reside in the TFS project they are associated with.
Has anyone used a seperate single monolithic project for bugs?
Is this supported out of the box by microsoft?
Will reporting be affected?
What are the reasons why we wouldn't want to have a single project?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
TFS 的一大优势是 MS 提供了从需求/规划到部署和测试的完整开发环境。工厂提供的默认流程模板对于快速启动您的开发工作具有真正的价值。 MS 在为您提供的默认流程模板中投入了大量精力，这些模板都是基于项目的（您的选项 2），这意味着它们假设您的项目已输入并且应在开发项目基础。应将错误输入到与其关联的 TFS 项目中。
现在，在一个项目中完成所有 QA 是完全不可能的吗？绝对不是！如果你有（非常）充分的理由这样做，它就可以实现。但是，您将在某些地方与系统作斗争，例如在报告和测试影响分析领域。我从经验中知道。一般来说，将 QA 项目的可追溯性与 TFS 项目上的代码和构建项目相关联并保证可追溯性。并且，您将无法重复使用提供的流程模板。它们必须在很大程度上进行定制。
嘿嘿，你已经付了系统费用了，而且还不便宜啊！尝试尽可能多地使用您所支付的费用，包括来自 MS 和社区支持的流程模板和工作方式，这将期望您遵循 MS 指南。
The BIG advantage of TFS is that MS delivers a complete development environment from requirement / planning to deployment and test. The factory delivered default process templates are of real value to quickly startup your development effort. MS have put a lot of effort in the default process templates provided to you, and those templates are all project based (your option 2), meaning that they assume your items are entered and should be tracked on a development project basis. The bugs should be entered in the TFS project they are associated with.
Now, is it completely impossible to do all QA in a single project? Absolutely not! If you have (very) good reasons to do so, it can be realized. But, you will be fighting the system in some places, for example in the area of reporting and test impact analysis. I know from experience. In general, associating and guarantying traceability of your QA items with code and build items over TFS projects. AND, you will not be able to re-use the supplied proces templates. They will have to be customized to a large extend.
Hey, you have paid for the system, and it is not cheap! Try to use as much of possible for what you have paid for, including the process templates and the way of working from MS and community support, which will expect you to follow the MS guidelines.