Read Continuous Integration. Making a "build" used to be a somewhat big ritual back in the days. Find "the machine" and "the files" with "the guy" and only he knows how to package everything up, etc... With CruiseControl and its cousins, unit tests are run, development builds are created, and installer is packaged automatically. There's nothing magical about any of the tools, but spending time setting each component up and maintaining them rewards the team greatly. Automated builds become a mundane part of life.
When you are working on a line of related projects, I'd suggest a strong coding conventions and policies so developers can read and share each others code. Part of the policy should be to prevent thing that can degrade modifiability of code; and to promote refactoring, unit tests, and DRY.
I am not going to repeat what's written by Fowler, but automating the deployment is also worth your time and effort (once you have something to deploy of course). From SQL scripts to creating service users, everything must be automated, and preferably wrapped in a simple website your testers can deploy on demand. Again, by automation, deploying QA builds to test become a matter of fact.
发布评论
评论（1）
三大秘诀。 自动化，自动化，自动化。
请阅读持续集成。 在过去，制作“构建”曾经是一个有点大的仪式。 与“那个人”一起查找“机器”和“文件”，只有他知道如何将所有内容打包等等...使用 CruiseControl 及其同类产品，运行单元测试，创建开发版本，并自动打包安装程序。 这些工具都没有什么神奇之处，但花时间设置每个组件并维护它们会给团队带来巨大的回报。 自动化构建成为生活中平凡的一部分。
当您从事一系列相关项目时，我建议采用强大的编码约定和策略，以便开发人员可以阅读和共享彼此的代码。 策略的一部分应该是防止可能降低代码可修改性的事情； 并促进重构、单元测试和DRY。
我不会重复 Fowler 所写的内容，但自动化部署也值得您花费时间和精力（当然，一旦您有需要部署的内容）。 从 SQL 脚本到创建服务用户，一切都必须自动化，并且最好封装在一个简单的网站中，测试人员可以根据需要进行部署。 同样，通过自动化，部署 QA 构建来进行测试已成为事实。
Top three tips. Automate, automate, automate.
Read Continuous Integration. Making a "build" used to be a somewhat big ritual back in the days. Find "the machine" and "the files" with "the guy" and only he knows how to package everything up, etc... With CruiseControl and its cousins, unit tests are run, development builds are created, and installer is packaged automatically. There's nothing magical about any of the tools, but spending time setting each component up and maintaining them rewards the team greatly. Automated builds become a mundane part of life.
When you are working on a line of related projects, I'd suggest a strong coding conventions and policies so developers can read and share each others code. Part of the policy should be to prevent thing that can degrade modifiability of code; and to promote refactoring, unit tests, and DRY.
I am not going to repeat what's written by Fowler, but automating the deployment is also worth your time and effort (once you have something to deploy of course). From SQL scripts to creating service users, everything must be automated, and preferably wrapped in a simple website your testers can deploy on demand. Again, by automation, deploying QA builds to test become a matter of fact.