- 1、本文档共15页,可阅读全部内容。
- 2、有哪些信誉好的足球投注网站(book118)网站文档一经付费(服务费),不意味着购买了该文档的版权,仅供个人/单位学习、研究之用,不得用于商业用途,未经授权,严禁复制、发行、汇编、翻译或者网络传播等,侵权必究。
- 3、本站所有内容均由合作方或网友上传,本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺!文档内容仅供研究参考,付费前请自行鉴别。如您付费,意味着您自己接受本站规则且自行承担风险,本站不退款、不进行额外附加服务;查看《如何避免下载的几个坑》。如果您已付费下载过本站文档,您可以点击 这里二次下载。
- 4、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等,请点击“版权申诉”(推荐),也可以打举报电话:400-050-0827(电话支持时间:9:00-18:30)。
查看更多
Daily Build and Smoke Test,User Experience,Not Metrics翻译论文
Daily Build and Smoke Test
If you want to create a simple computer program consisting of only one file, you merely need to compile and link that one file. On a typical team project involving dozens, hundreds, or even thousands of files, however, the process of creating an executable program becomes more complicated and time consuming. You must build the program from its various components.
A common practice at Microsoft and some other shrink-wrap software companies is the daily build and smoke test process. Every file is compiled, linked, and combined into an executable program every day, and the program is then put through a smoke test, a relatively simple check to see whether the product smokes when it runs.
BENEFITS.?This simple process produces several significant benefits.
It minimizes integration risk.?One of the greatest risks that a team project faces is that, when the different team members combine or integrate the code they have been working on separately, the resulting composite code does not work well. Depending on how late in the project the incompatibility is discovered, debugging might take longer than it would have if integration had occurred earlier, program interfaces might have to be changed, or major parts of the system might have to be redesigned and reimplemented. In extreme cases, integration errors have caused projects to be cancelled. The daily build and smoke test process keeps integration errors small and manageable, and it prevents runaway integration problems.
It reduces the risk of low quality.?Related to the risk of unsuccessful or problematic integration is the risk of low quality. By minimally smoke-testing all the code daily, quality problems are prevented from taking control of the project. You bring the system to a known, good state, and then you keep it there. You simply dont allow it to deteriorate to the point where time-consuming quality problems can occur.
It supports easier defect diagnosis.?When the product is built and tes
您可能关注的文档
- unit8人教版知识点汇总.doc
- 足球术语中英文对照资料.doc
- 【24C】Characterization of Waste in Building Construction Projects.doc
- 七年级下册英语第九单元复习教案.doc
- 英语_7-12.doc
- 七年级下册Unit 9 What does he look like重难点.doc
- Unity3d_10_Building ScenesPrefabs中文翻译.doc
- 高二第一学期英语单词.docx
- GCT核心词汇.docx
- 7.11.B11 - 抹灰及油漆涂料-Plasterwork and Building Painting.docx
文档评论(0)