TFSBuild.Proj 和手动 SQL Server 工作有帮助吗？
使用 VS 2008 GDR 更新，我创建了一个数据库项目。我已经创建了一个 SQL Server 部署包。我创建了一个数据库单元测试。
使用一些向导，这些内容进入了我的 tfsbuild.proj 文件，因此在自动构建过程即将结束时创建了一个数据库。
我现在明白了，我对整个过程缺乏一点控制。我想做的是手动部署数据库，针对数据库运行 3 个自定义脚本，然后手动启动数据库单元测试。我已经运行了其他非数据库单元测试。我不想使用 VSMDI 或有序的单元测试内容，因为在多开发人员环境中它会变得混乱。
帮助！
Using the VS 2008 GDR update, I have created a database project. I have created a SQL Server deployment package. I have created a database unit test.
Using some wizards, the stuff got into my tfsbuild.proj file so near the end of the automated build process a database is created.
I lack a little control of the whole process, I now see. What I would like to do is manually deploy the DB, run 3 custom scripts against the DB, and then manually start the DB unit test. I have other non-DB unit tests that already run. I do not want to use VSMDI or ordered unit test stuff because in out multi-developer environment it gets messy.
Help!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
也许我误读或遗漏了一些细节，但在我看来，问题在于分支管理，而不是自动化测试。大多数组织绝对愿意达到您所在的位置，全自动构建和数据库单元测试。
如果在多开发环境中变得混乱，则可能表明开发人员正在直接检查运行自动化测试的分支。理想情况下，您应该只在重要分支上运行 BVT，并让开发人员签入私有分支。私有分支经过手动测试，然后在适当的时候进行反向集成（功能完整、稳定的里程碑等）。自动化构建和测试流程会进行反向集成签入并删除新构建，运行 BVT 等。通过这种方式，您可以将连续集成和 BVT 流程与不完整功能的流失或持续签入隔离开来。
Perhaps I'm misreading or missing some details, but it seems to me that the problem is branch management, not automated testing. Most orgs would absolutely love to get to where you are, full automated build and DB unit test.
If it gets messy in a multi-development environment it may indicate developers are checking straight into a branch that runs automated tests. Ideally you should only run BVTs on the important branches and let developers check in into private branches. Private branches are manually tested, then reverse integrated when appropriate (feature complete, stable milestone etc). The automated build and test process picks up the reverse integration check in and drops a new build, running the BVTs and all that. This way you isolated the contiguous integration and BVT process from the churn or constant check in of incomplete features.