SVN 上 .NET 项目的 QA 构建自动化机制
我们正在开发 .NET Windows 应用程序。我们从一开始就使用 TFS。现在，在 Assembla 之后 - 一个敏捷的 wiki 项目管理和协作工具，为 SVN 上的源代码控制提供存储库，我们正在迁移从 TFS 到 SVN。
当我们开始如何为我们的 QA 提供（每周）构建时，我们并没有烦恼。但是，当我们开始使用 Assembla 并针对开放票据填充补丁并将其重新分配给 QA 时。他们现在需要最新版本来审查问题并更新票证状态。之前的测试方法是我们每周向他们提供 Mercury QC 上的构建和更新缺陷状态，以修复。现在，不再有每周构建。他们现在必须进行构建，因为他们看到票证已更新为“准备测试”。
您有何建议？我应该建议采用什么方法来为我们的 QA 自动化此构建过程，以便他们可以在自己这边生成构建，并可以快速查看票证中提到的问题详细信息并将其标记为“已修复”或“重新打开”。
谢谢。
We are working on .NET Windows Application. We were using TFS from the beginning. Now, after Assembla - an agile wiki project management and collabration tool that provides a repository for source control which is on SVN we are moving from TFS to SVN.
We didn't bother when we started how would we provide (weekly) builds to our QA. But, as we started using Assembla and filling our patches against open Tickets and reassign it to QA. They now need to have a latest build to review the issue and update the status of the ticket. Prior method of testing was we provide them weekly build and updated defects status on Mercury QC to Fixed. Now, there is no more weekly build. They now have to build as they see a ticket has been updated to 'Ready for Test'.
What would you suggest what method should I suggest to automate this build process for our QA so they can generate builds at their side and can quickly review the issue details mentioned in the ticket and marked it Fixed or REOPENED.
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
JetBrains Teamcity 是一个可用于执行此操作的持续集成系统。
JetBrains Teamcity is one continuous integration system you could use to do this.