<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta charset="utf-8">
<meta name="generator" content="pdf2htmlEX">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<link rel="stylesheet" href="https://static.pudn.com/base/css/base.min.css">
<link rel="stylesheet" href="https://static.pudn.com/base/css/fancy.min.css">
<link rel="stylesheet" href="https://static.pudn.com/prod/directory_preview_static/6272bf7c40256a40ce0ad564/raw.css">
<script src="https://static.pudn.com/base/js/compatibility.min.js"></script>
<script src="https://static.pudn.com/base/js/pdf2htmlEX.min.js"></script>
<script>
try{
pdf2htmlEX.defaultViewer = new pdf2htmlEX.Viewer({});
}catch(e){}
</script>
<title></title>
</head>
<body>
<div id="sidebar" style="display: none">
<div id="outline">
</div>
</div>
<div id="pf1" class="pf w0 h0" data-page-no="1"><div class="pc pc1 w0 h0"><img class="bi x0 y0 w1 h1" alt="" src="https://static.pudn.com/prod/directory_preview_static/6272bf7c40256a40ce0ad564/bg1.jpg"><div class="t m0 x1 h2 y1 ff1 fs0 fc0 sc0 ls0 ws0">1</div><div class="t m0 x2 h3 y2 ff2 fs1 fc0 sc0 ls0 ws0">Bug<span class="_"> </span><span class="ff3">管<span class="_ _0"></span>理的经<span class="_ _0"></span>验和<span class="_ _0"></span>实践<span class="_ _0"></span>（下<span class="_ _0"></span>）</span></div><div class="t m0 x2 h4 y3 ff3 fs2 fc0 sc0 ls0 ws0">孟岩：刘振飞，<span class="_ _1"></span>你好。在这个系<span class="_ _1"></span>列的前面两篇<span class="_ _1"></span>文章里，我们先<span class="_ _1"></span>是探讨了<span class="_ _2"> </span><span class="ff1">Bug<span class="_ _2"> </span></span>管理的理念和</div><div class="t m0 x2 h4 y4 ff3 fs2 fc0 sc0 ls0 ws0">意义，然后又从<span class="_ _1"></span>软件系统的构建<span class="_ _1"></span>角度更进一步<span class="_ _1"></span>探讨了<span class="_ _2"> </span><span class="ff1">Bug<span class="_ _2"> </span></span>管理技术层面的问<span class="_ _1"></span>题。这次我想</div><div class="t m0 x2 h4 y5 ff3 fs2 fc0 sc0 ls0 ws0">我们应该来探<span class="_ _1"></span>讨<span class="_ _3"> </span><span class="ff1">Bug<span class="_"> </span></span>管理<span class="_ _1"></span>中人<span class="_ _1"></span>的<span class="_ _1"></span>问题了。<span class="_ _1"></span>当然，<span class="_ _1"></span>所谓人的<span class="_ _1"></span>问题，<span class="_ _1"></span>就是管理制度<span class="_ _1"></span>的问题。</div><div class="t m0 x2 h4 y6 ff3 fs2 fc0 sc0 ls0 ws0">有了先进的理念<span class="_ _1"></span>、坚实的软硬件<span class="_ _1"></span>基础，还需要<span class="_ _1"></span>有相应的管理制<span class="_ _1"></span>度与之相配套<span class="_ _1"></span>，否则<span class="_ _2"> </span><span class="ff1">Bug<span class="_ _2"> </span></span>管</div><div class="t m0 x2 h4 y7 ff3 fs2 fc0 sc0 ls0 ws0">理就只是一个摆<span class="_ _1"></span>设。你认为一个<span class="_ _1"></span>软件开发团队<span class="_ _1"></span>应当制定严格<span class="_ _1"></span>的<span class="_ _2"> </span><span class="ff1">Bug<span class="_ _4"> </span></span>管理制度吗？没<span class="_ _1"></span>有一个</div><div class="t m0 x2 h5 y8 ff3 fs2 fc0 sc0 ls0 ws0">相配套的管理制<span class="_ _1"></span>度，会有怎样的<span class="_ _1"></span>后果？</div><div class="t m0 x2 h5 y9 ff3 fs2 fc1 sc0 ls0 ws0">刘振飞：我们在<span class="_ _1"></span>第一篇文章中讨<span class="_ _1"></span>论过，微软的<span class="_ _1"></span>软件研发可以总<span class="_ _1"></span>结为以下两点<span class="_ _1"></span>：</div><div class="t m0 x2 h4 ya ff3 fs2 fc1 sc0 ls0 ws0">（<span class="ff1">1</span>）<span class="_ _5"></span>．需求（<span class="_ _1"></span><span class="ff1">PM<span class="ff3">）<span class="_ _5"></span>、开发<span class="_ _1"></span>（<span class="ff1">Dev</span>）<span class="_ _5"></span>、测试（<span class="_ _1"></span><span class="ff1">T<span class="_ _6"></span>est<span class="ff3">）三权分立<span class="_ _1"></span>，分工明确、<span class="_ _1"></span>各司其职</span></span></span></span></div><div class="t m0 x2 h4 yb ff3 fs2 fc1 sc0 ls0 ws0">（<span class="ff1">2</span>）<span class="_ _5"></span>．每个产品<span class="_ _1"></span>的每个版本遵循<span class="_ _1"></span>同样的模式：<span class="_ _1"></span>流程＋工具＋人<span class="_ _1"></span>，并不断反馈<span class="_ _1"></span>（以改进流程<span class="_ _1"></span>、</div><div class="t m0 x2 h4 yc ff3 fs2 fc1 sc0 ls0 ws0">升级工具并提高<span class="_ _1"></span>团队<span class="ff1">/</span>员工<span class="_ _1"></span>的能力）</div><div class="t m0 x3 h4 yd ff3 fs2 fc1 sc0 ls0 ws0">回到你这个问题<span class="_ _1"></span>，<span class="ff1">Bug<span class="_ _7"> </span></span>管理制度其实<span class="_ _1"></span>就是定义<span class="_ _7"> </span><span class="ff1">Bug<span class="_ _7"> </span></span>处理流程，<span class="_ _1"></span>有了好用的工<span class="_ _1"></span>具之后，</div><div class="t m0 x2 h6 ye ff3 fs2 fc1 sc0 ls0 ws0">我们需要这样的<span class="_ _1"></span>流程去明确指导<span class="_ _1"></span>如何对<span class="_ _8"> </span><span class="ff1">Bug<span class="_ _8"> </span></span>进行管理。但<span class="_ _1"></span>是一个软件开<span class="_ _1"></span>发团队应当制定<span class="_ _1"></span><span class="fs3 fc2">严</span></div><div class="t m0 x2 h6 yf ff3 fs3 fc2 sc0 ls0 ws0">格的<span class="_ _9"> </span><span class="ff1 fs2 fc1">Bug<span class="_"> </span><span class="ff3">管理</span></span>制度<span class="fs2 fc1">吗？<span class="_ _1"></span>坦率的讲，<span class="_ _a"></span>不需要。<span class="_ _a"></span>严格的制度<span class="_ _1"></span>在软件行业就<span class="_ _1"></span>意味着教条、<span class="_ _a"></span>负担和</span></div><div class="t m0 x2 h5 y10 ff3 fs2 fc1 sc0 ls0 ws0">不切实际，让一<span class="_ _1"></span>帮聪明的大脑陷<span class="_ _1"></span>入无边无际的<span class="_ _1"></span>条条框框不能自<span class="_ _1"></span>拔，明知道是<span class="_ _1"></span>包袱还要去背<span class="_ _1"></span>、</div><div class="t m0 x2 h5 y11 ff3 fs2 fc1 sc0 ls0 ws0">是火坑还要去跳<span class="_ _1"></span>，<span class="_ _a"></span>直<span class="_ _1"></span>到有一天终于受<span class="_ _1"></span>不了，<span class="_ _a"></span>最<span class="_ _1"></span>终结果不外乎三<span class="_ _1"></span>个：<span class="_ _b"></span>过劳累到、<span class="_ _b"></span>对付一天<span class="_ _1"></span>是一</div><div class="t m0 x2 h4 y12 ff3 fs2 fc1 sc0 ls0 ws0">天或者干脆辞职<span class="_ _1"></span>换个工作。<span class="_ _c"></span>因此我觉得应<span class="_ _1"></span>该用<span class="_ _c"></span><span class="ff1">Bug<span class="_"> </span></span>管理指导原<span class="_ _1"></span>则<span class="_ _d"></span>（<span class="ff1">guidanc<span class="_ _1"></span>e<span class="ff3">）<span class="_ _5"></span><span class="_ _c"></span>来替换<span class="_ _d"></span><span class="ff1">Bug</span></span></span></div><div class="t m0 x2 h4 y13 ff3 fs2 fc1 sc0 ls0 ws0">管理规章制度（<span class="ff1">r<span class="_ _1"></span>ules<span class="_"> </span>&<span class="_"> </span>reg<span class="_ _1"></span>ulations<span class="ff3">）<span class="_ _5"></span>这个词<span class="_ _1"></span>。</span></span></div><div class="t m0 x3 h7 y14 ff3 fs2 fc1 sc0 ls0 ws0">所以我认为<span class="_ _3"> </span><span class="ff1">Bug<span class="_"> </span></span>管理就是<span class="_ _1"></span>去<span class="fc3">制定适合自己团队实际情况的<span class="_ _3"> </span><span class="ff2">Bug<span class="_"> </span></span>处理流程和指导原则</span>，</div><div class="t m0 x2 h5 y15 ff3 fs2 fc1 sc0 ls0 ws0">制定者（管理层<span class="_ _1"></span>）应该起到真正<span class="_ _1"></span>指导的作用，<span class="_ _1"></span>他们要非常清楚<span class="_ _1"></span>下面这些问题<span class="_ _1"></span>的答案：</div><div class="t m0 x3 h8 y16 ff4 fs2 fc1 sc0 ls0 ws0">l<span class="_ _e"> </span><span class="ff3">我们需要测试什<span class="_ _1"></span>么：哪些软件（<span class="_ _1"></span>网站）<span class="_ _5"></span>、哪些<span class="_ _1"></span>模块</span></div><div class="t m0 x3 h8 y17 ff4 fs2 fc1 sc0 ls0 ws0">l<span class="_ _e"> </span><span class="ff3">测试人员的分工<span class="_ _1"></span>：什么人负责什<span class="_ _1"></span>么模块</span></div><div class="t m0 x3 h8 y18 ff4 fs2 fc1 sc0 ls0 ws0">l<span class="_ _e"> </span><span class="ff3">测试工具和环境<span class="_ _1"></span>：<span class="_ _b"></span>巧<span class="_ _1"></span>妇难为无米之炊<span class="_ _1"></span>。<span class="_ _f"></span>你不能安排一个测<span class="_ _1"></span>试人员去测某<span class="_ _1"></span>个模块，<span class="_ _f"></span>而</span></div><div class="t m0 x4 h5 y19 ff3 fs2 fc1 sc0 ls0 ws0">没有给他提供必<span class="_ _1"></span>要的软硬件环境</div><div class="t m0 x3 h8 y1a ff4 fs2 fc1 sc0 ls0 ws0">l<span class="_ _e"> </span><span class="ff3">测试的进度安排<span class="_ _1"></span>：<span class="_ _b"></span>干这一行加班是不<span class="_ _1"></span>可避免的，<span class="_ _b"></span>但是需要<span class="_ _1"></span>有度，<span class="_ _b"></span>人不是机器<span class="_ _1"></span>，<span class="_ _b"></span>长期</span></div><div class="t m0 x4 h5 y1b ff3 fs2 fc1 sc0 ls0 ws0">的劳累谁都扛不<span class="_ _1"></span>住。如果时间很<span class="_ _1"></span>紧，那只能去<span class="_ _1"></span>抓重点，要有所<span class="_ _1"></span>不为</div><div class="t m0 x3 h8 y1c ff4 fs2 fc1 sc0 ls0 ws0">l<span class="_ _e"> </span><span class="ff3">发现一个问题时<span class="_ _1"></span>，如何用<span class="_ _10"> </span><span class="ff1">Bug<span class="_"> </span></span>管理工具<span class="_ _1"></span>去创建一个<span class="_ _10"> </span><span class="ff1">Bug</span>：标<span class="_ _1"></span>题如何写、<span class="_ _1"></span>严重程度、</span></div><div class="t m0 x4 h4 y1d ff3 fs2 fc1 sc0 ls0 ws0">详细重现步骤、<span class="_ _1"></span>错误状况、期望<span class="_ _1"></span>结果、现场附<span class="_ _1"></span>件、这个<span class="_ _10"> </span><span class="ff1">Bug<span class="_"> </span></span>去分配给谁</div><div class="t m0 x3 h8 y1e ff4 fs2 fc1 sc0 ls0 ws0">l<span class="_ _e"> </span><span class="ff3">当一个<span class="_ _10"> </span><span class="ff1">B<span class="_ _0"></span>ug<span class="_"> </span></span>被处理<span class="_ _1"></span>掉时，测试人<span class="_ _1"></span>员应该如何验<span class="_ _1"></span>证并关闭</span></div><div class="t m0 x3 h8 y1f ff4 fs2 fc1 sc0 ls0 ws0">l<span class="_ _e"> </span><span class="ff3">当一个<span class="_ _10"> </span><span class="ff1">B<span class="_ _0"></span>ug<span class="_"> </span></span>的解决<span class="_ _1"></span>方法有争议时<span class="_ _1"></span>，谁来仲裁</span></div><div class="t m0 x3 h8 y20 ff4 fs2 fc1 sc0 ls0 ws0">l<span class="_ _e"> </span><span class="ff3">定期的<span class="_ _10"> </span><span class="ff1">B<span class="_ _0"></span>ug<span class="_"> </span></span>提醒，<span class="_ _1"></span>比如当前每个<span class="_ _1"></span>人的<span class="_ _3"> </span><span class="ff1">Bug<span class="_"> </span></span>情<span class="_ _1"></span>况</span></div><div class="t m0 x3 h8 y21 ff4 fs2 fc1 sc0 ls0 ws0">l<span class="_ _e"> </span><span class="ff1">Bug<span class="_"> </span><span class="ff3">状态报告<span class="_ _1"></span>：<span class="ff1">Bug<span class="_"> </span></span>数目<span class="_ _1"></span>的变化趋势及我<span class="_ _1"></span>们应该采取的行<span class="_ _1"></span>动</span></span></div><div class="t m0 x3 h8 y22 ff4 fs2 fc1 sc0 ls0 ws0">l<span class="_ _e"> </span><span class="ff3">阶段性的总结反<span class="_ _1"></span>馈：哪些地方我<span class="_ _1"></span>们做的好，哪<span class="_ _1"></span>些做的不好，为<span class="_ _1"></span>什么、如何改<span class="_ _1"></span>进</span></div><div class="t m0 x3 h8 y23 ff4 fs2 fc1 sc0 ls0 ws0">l<span class="_ _e"> </span><span class="ff1">…<span class="_"> </span>…</span></div><div class="t m0 x2 h4 y24 ff3 fs2 fc1 sc0 ls0 ws0">没有这样配套<span class="_ _1"></span>的<span class="_ _2"> </span><span class="ff1">Bug<span class="_ _4"> </span></span>处理流程和指导<span class="_ _1"></span>原则，再好的<span class="_ _1"></span>工具都将会是一<span class="_ _1"></span>个摆设、甚至是<span class="_ _1"></span>添乱的</div><div class="t m0 x2 h5 y25 ff3 fs2 fc1 sc0 ls0 ws0">工具。<span class="_ _c"></span>就像一个乐队<span class="_ _1"></span>有非常出色的各<span class="_ _1"></span>种乐器，<span class="_ _c"></span>但乐队指挥<span class="_ _1"></span>是个外行<span class="_ _c"></span>（就像成<span class="_ _1"></span>龙电影<span class="_ _c"></span>《双龙会》</div><div class="t m0 x2 h5 y26 ff3 fs2 fc1 sc0 ls0 ws0">一个镜头）<span class="_ _5"></span>，那<span class="_ _1"></span>么演奏出来<span class="_ _1"></span>的一定会是混乱<span class="_ _1"></span>的乐章。</div><a class="l" rel='nofollow' onclick='return false;'><div class="d m1"></div></a></div><div class="pi" data-data='{"ctm":[1.611850,0.000000,0.000000,1.611850,0.000000,0.000000]}'></div></div>
</body>
</html>
<div id="pf2" class="pf w0 h0" data-page-no="2"><div class="pc pc2 w0 h0"><img class="bi x0 y0 w1 h1" alt="" src="https://static.pudn.com/prod/directory_preview_static/6272bf7c40256a40ce0ad564/bg2.jpg"><div class="t m0 x1 h2 y1 ff1 fs0 fc0 sc0 ls0 ws0">2</div><div class="t m0 x2 h4 y27 ff3 fs2 fc0 sc0 ls0 ws0">孟岩：根据你的<span class="_ _1"></span>了解，国内中小<span class="_ _1"></span>型软件开发企<span class="_ _1"></span>业中<span class="_ _2"> </span><span class="ff1">Bug<span class="_ _2"> </span></span>管理制度方面有什<span class="_ _1"></span>么缺陷？主要<span class="_ _1"></span>的</div><div class="t m0 x2 h5 y28 ff3 fs2 fc0 sc0 ls0 ws0">问题是什么？</div><div class="t m0 x2 h4 y29 ff3 fs2 fc1 sc0 ls0 ws0">刘振飞：我想目<span class="_ _1"></span>前中小软件企业<span class="_ _1"></span>的<span class="_ _10"> </span><span class="ff1">B<span class="_ _0"></span>ug<span class="_"> </span></span>管理主要<span class="_ _1"></span>存在的问题是<span class="_ _1"></span>：</div><div class="t m0 x2 h4 y2a ff1 fs2 fc1 sc0 ls0 ws0">1.<span class="_ _11"> </span><span class="ff3">不重视测试，认<span class="_ _1"></span>为测试人员无关<span class="_ _1"></span>大局，随便测<span class="_ _1"></span>测就行了。当然<span class="_ _1"></span>这种情况正在<span class="_ _1"></span>逐步好转，</span></div><div class="t m0 x3 h5 y2b ff3 fs2 fc1 sc0 ls0 ws0">因为大家都开始<span class="_ _1"></span>意识到了测试重<span class="_ _1"></span>要性；</div><div class="t m0 x2 h4 y2c ff1 fs2 fc1 sc0 ls0 ws0">2.<span class="_ _11"> </span><span class="ff3">有些企业，<span class="_ _f"></span>认识到测<span class="_ _1"></span>试的重要性后，<span class="_ _f"></span>却走<span class="_ _1"></span>向极端<span class="_ _12"> </span><span class="ff1">---<span class="_ _12"> </span></span>制定<span class="_ _1"></span>了极其严格的<span class="_ _1"></span>规章制度：<span class="_ _f"></span>无数</span></div><div class="t m0 x3 h4 y2d ff3 fs2 fc1 sc0 ls0 ws0">琐碎、难用的测<span class="_ _1"></span>试工单、非常严<span class="_ _1"></span>密的一级级权<span class="_ _1"></span>力控制，在<span class="_ _2"> </span><span class="ff1">Bug<span class="_ _2"> </span></span>管理系统中谁<span class="_ _1"></span>能看到什</div><div class="t m0 x3 h5 y2e ff3 fs2 fc1 sc0 ls0 ws0">么信息、<span class="_ _b"></span>谁可以解决<span class="_ _1"></span>、<span class="_ _b"></span>谁可以关闭等等，<span class="_ _f"></span>非常严格。<span class="_ _b"></span>一个需要灵活<span class="_ _1"></span>变化的工作变成<span class="_ _1"></span>了工</div><div class="t m0 x3 h5 y2f ff3 fs2 fc1 sc0 ls0 ws0">业制造车间流水<span class="_ _1"></span>线的一个工种，<span class="_ _c"></span>让测试人<span class="_ _1"></span>员陷入制度的泥<span class="_ _1"></span>潭，<span class="_ _c"></span>不能把主要精力投入<span class="_ _1"></span>测试</div><div class="t m0 x3 h5 y30 ff3 fs2 fc1 sc0 ls0 ws0">工作本身；</div><div class="t m0 x2 h4 y31 ff1 fs2 fc1 sc0 ls0 ws0">3.<span class="_ _11"> </span><span class="ff3">管理层自身没有<span class="_ _1"></span>制订明确的<span class="_ _10"> </span><span class="ff1">Bug<span class="_"> </span></span>处理流程及<span class="_ _1"></span>相关指导原则<span class="_ _1"></span>，<span class="_ _b"></span>让测试人员在黑<span class="_ _1"></span>暗中摸索，</span></div><div class="t m0 x3 h5 y32 ff3 fs2 fc1 sc0 ls0 ws0">走到哪儿算哪儿<span class="_ _1"></span>，不能给他们以<span class="_ _1"></span>切实有效的指<span class="_ _1"></span>导和帮助；</div><div class="t m0 x2 h4 y33 ff1 fs2 fc1 sc0 ls0 ws0">4.<span class="_ _11"> </span><span class="ff3">管理层把软件的<span class="_ _1"></span>质量保证责任一<span class="_ _1"></span>股脑推到测试<span class="_ _1"></span>人员身上，<span class="_ _13"></span>任何问题都<span class="_ _1"></span>去指责下面的测<span class="_ _1"></span>试</span></div><div class="t m0 x3 h5 y34 ff3 fs2 fc1 sc0 ls0 ws0">人员，殊不知测<span class="_ _1"></span>试仅仅是研发的<span class="_ _1"></span>一个环节，前<span class="_ _1"></span>面需求、开发两<span class="_ _1"></span>个环节如果没<span class="_ _1"></span>有好好做，</div><div class="t m0 x3 h5 y35 ff3 fs2 fc1 sc0 ls0 ws0">测试将会极其被<span class="_ _1"></span>动，比如：没有<span class="_ _1"></span>需求文档，怎<span class="_ _1"></span>么测试？这是一<span class="_ _1"></span>个系统工程；</div><div class="t m0 x2 h4 y36 ff1 fs2 fc1 sc0 ls0 ws0">5.<span class="_ _11"> </span><span class="ff3">错误的考核标准<span class="_ _1"></span>：管理层用<span class="_ _9"> </span><span class="ff1">Bug<span class="_ _9"> </span></span>个数<span class="_ _1"></span>去衡量测试人<span class="_ _1"></span>员的工作成绩，<span class="_ _1"></span>谁发现的<span class="_ _9"> </span><span class="ff1">Bug<span class="_ _9"> </span></span>多谁</span></div><div class="t m0 x3 h4 y37 ff3 fs2 fc1 sc0 ls0 ws0">的工作就做的好<span class="_ _1"></span>。这是一个十分<span class="_ _1"></span>危险的倾向，<span class="_ _1"></span>将直接导致测试<span class="_ _1"></span>人员去重视<span class="_ _7"> </span><span class="ff1">Bug<span class="_ _4"> </span></span>个数这</div><div class="t m0 x3 h5 y38 ff3 fs2 fc1 sc0 ls0 ws0">个数字本身、而<span class="_ _1"></span>不是产品的真正<span class="_ _1"></span>质量。</div><div class="t m0 x4 h5 y39 ff3 fs2 fc1 sc0 ls0 ws0">遗憾的是，<span class="_ _14"></span>即使在微软内<span class="_ _1"></span>部，<span class="_ _14"></span>各个地方研发中心<span class="_ _1"></span>也有这个倾向<span class="_ _1"></span>，<span class="_ _14"></span>比如经常出现大陆<span class="_ _1"></span>、</div><div class="t m0 x3 h5 y3a ff3 fs2 fc1 sc0 ls0 ws0">台湾、<span class="_ _5"></span>韩国、<span class="_ _13"></span>日本四个地<span class="_ _1"></span>方某个软件的<span class="_ _1"></span>测试人员虎视<span class="_ _1"></span>眈眈的在半夜盯<span class="_ _1"></span>着某个版本的问<span class="_ _1"></span>世，</div><div class="t m0 x3 h4 y3b ff3 fs2 fc1 sc0 ls0 ws0">一<span class="_ _0"></span>旦<span class="_ _0"></span>下<span class="_ _15"></span>载到<span class="_ _15"></span>最<span class="_ _0"></span>新<span class="_ _0"></span>的<span class="_ _16"> </span><span class="ff1">Build</span>，<span class="_ _15"></span>马<span class="_ _0"></span>上<span class="_ _0"></span>安<span class="_ _0"></span>装<span class="_ _15"></span>测<span class="_ _0"></span>试<span class="_ _0"></span>，<span class="_ _0"></span>把<span class="_ _15"></span>表<span class="_ _0"></span>面<span class="_ _0"></span>上<span class="_ _0"></span>的<span class="_ _16"> </span><span class="ff1">Bug<span class="_ _16"> </span></span>赶快<span class="_ _0"></span><span class="_ _15"></span>抢<span class="_ _15"></span>到、<span class="_ _15"></span>记<span class="_ _0"></span>录<span class="_ _0"></span>进</div><div class="t m0 x3 h4 y3c ff1 fs2 fc1 sc0 ls0 ws0">Raid/Product<span class="_ _7"> </span>Studio<span class="_"> </span><span class="ff3">中，然<span class="_ _1"></span>后心满意足的打<span class="_ _1"></span>车回去，很高兴<span class="_ _1"></span>比另外三个对<span class="_ _1"></span>手多上了几个</span></div><div class="t m0 x3 h4 y3d ff1 fs2 fc1 sc0 ls0 ws0">Bug<span class="ff3">。<span class="_ _f"></span>我记得微软内部<span class="_ _1"></span>有个专门的培训<span class="_ _1"></span>曾认真的研讨<span class="_ _1"></span>过这个问题：<span class="_ _f"></span>不能用<span class="_ _10"> </span><span class="ff1">Bug<span class="_"> </span></span>数目来衡</span></div><div class="t m0 x3 h4 y3e ff3 fs2 fc1 sc0 ls0 ws0">量<span class="_ _12"> </span><span class="ff1">T<span class="_ _6"></span>ester<span class="_ _12"> </span><span class="ff3">的工作。但是微软太大了，当某地<span class="_ _1"></span>方或部门不能找到更合适的标准<span class="_ _1"></span>的时候，</span></span></div><div class="t m0 x3 h4 y3f ff1 fs2 fc1 sc0 ls0 ws0">Bug<span class="_"> </span><span class="ff3">数目本身<span class="_ _1"></span>就是最快捷<span class="_ _1"></span>的答案了。</span></div><div class="t m0 x4 h5 y40 ff3 fs2 fc1 sc0 ls0 ws0">这是我现在经常<span class="_ _1"></span>思考的问题之一<span class="_ _1"></span>。</div><div class="t m0 x2 h4 y41 ff3 fs2 fc0 sc0 ls0 ws0">孟岩：能否请你<span class="_ _1"></span>比较系统地阐述<span class="_ _1"></span>一下微软的<span class="_ _10"> </span><span class="ff1">Bug<span class="_"> </span></span>管理制度<span class="_ _1"></span>？</div><div class="t m0 x2 h4 y42 ff3 fs2 fc1 sc0 ls0 ws0">刘振飞：<span class="_ _6"></span>其实前<span class="_ _1"></span>两篇文章已经陆<span class="_ _1"></span>续谈过微软<span class="_ _1"></span>的<span class="_ _3"> </span><span class="ff1">Bug<span class="_"> </span></span>管理指<span class="_ _1"></span>导原则了，<span class="_ _6"></span>这里系<span class="_ _1"></span>统的总结一下<span class="_ _1"></span>：</div><div class="t m0 x2 h8 y43 ff4 fs2 fc1 sc0 ls0 ws0">u<span class="_ _e"> </span><span class="ff3">管理层要求所有<span class="_ _1"></span>的<span class="_ _3"> </span><span class="ff1">Bug<span class="_"> </span></span>都要通过<span class="_ _3"> </span><span class="ff1">Raid</span>（<span class="ff1">Product<span class="_ _12"> </span>S<span class="_ _1"></span>tudio<span class="ff3">）来跟<span class="_ _1"></span>踪处理。这个<span class="_ _1"></span>看起来很简</span></span></span></div><div class="t m0 x3 h4 y44 ff3 fs2 fc1 sc0 ls0 ws0">单的<span class="_ _10"> </span><span class="ff1">B<span class="_ _0"></span>ug<span class="_"> </span></span>管理工具<span class="_ _1"></span>是每个员工和<span class="_ _1"></span>其他同事有效<span class="_ _1"></span>协作的重要保证</div><div class="t m0 x2 h8 y45 ff4 fs2 fc1 sc0 ls0 ws0">u<span class="_ _e"> </span><span class="ff3">每个产品都细分<span class="_ _1"></span>模块<span class="_ _a"></span>（<span class="ff1">Area</span>，<span class="_ _6"></span><span class="ff1">SubArea<span class="_ _1"></span><span class="ff3">）<span class="_ _5"></span>，<span class="_ _6"></span>每个模块都<span class="_ _1"></span>有明确的需求定<span class="_ _1"></span>义者<span class="_ _a"></span>（<span class="ff1">PM</span>）<span class="_ _5"></span>、<span class="_ _6"></span>开发</span></span></span></div><div class="t m0 x3 h4 y46 ff3 fs2 fc1 sc0 ls0 ws0">工程师<span class="_ _0"></span>（<span class="ff1">Dev</span>）<span class="_ _0"></span>和测试<span class="_ _0"></span>工程师<span class="_ _0"></span>（<span class="ff1">T<span class="_ _6"></span>ester<span class="ff3">）这<span class="_ _0"></span>三个角<span class="_ _0"></span>色。一个<span class="_ _0"></span>问题出<span class="_ _0"></span>现了，<span class="_ _0"></span>一定会<span class="_ _0"></span>落实<span class="_ _0"></span>到</span></span></div><div class="t m0 x3 h4 y47 ff3 fs2 fc1 sc0 ls0 ws0">某个人的头上去<span class="_ _1"></span>跟踪处理，绝不<span class="_ _1"></span>能出现无主<span class="_ _1"></span>的<span class="_ _10"> </span><span class="ff1">Bug</span></div><div class="t m0 x2 h8 y48 ff4 fs2 fc1 sc0 ls0 ws0">u<span class="_ _e"> </span><span class="ff1">PM<span class="_ _8"> </span><span class="ff3">负责<span class="_ _1"></span>书写的<span class="_ _8"> </span><span class="ff1">Spe<span class="_ _1"></span>c<span class="_ _8"> </span><span class="ff3">是这<span class="_ _1"></span>个功能特征（<span class="ff1">F<span class="_ _1"></span>eature<span class="ff3">）的合同<span class="_ _1"></span><span class="_ _5"></span>，以此<span class="_ _8"> </span><span class="ff1">S<span class="_ _1"></span>pec<span class="_ _8"> </span><span class="ff3">来指<span class="_ _1"></span>导开发和</span></span></span></span></span></span></span></span></div><div class="t m0 x3 h4 y49 ff3 fs2 fc1 sc0 ls0 ws0">测试。当<span class="_ _10"> </span><span class="ff1">Dev<span class="_"> </span></span>和<span class="_ _3"> </span><span class="ff1">T<span class="_ _6"></span>ester<span class="_"> </span><span class="ff3">就<span class="_ _1"></span>某个<span class="_ _3"> </span><span class="ff1">Bug<span class="_"> </span></span>发生<span class="_ _1"></span>争执的时候<span class="_ _1"></span>，<span class="ff1">PM<span class="_"> </span></span>负责给出<span class="_ _1"></span>一个明确的<span class="_ _1"></span>说明</span></span></div><div class="t m0 x2 h8 y4a ff4 fs2 fc1 sc0 ls0 ws0">u<span class="_ _e"> </span><span class="ff3">测试不仅仅是<span class="_ _10"> </span><span class="ff1">T<span class="_ _6"></span>ester<span class="_"> </span><span class="ff3">的事<span class="_ _1"></span>情，<span class="_ _17"></span>尽管那是他们<span class="_ _1"></span>的专职工作<span class="_ _1"></span>。<span class="_ _17"></span>研发团队中的所<span class="_ _1"></span>有人每发现产</span></span></span></div><div class="t m0 x3 h5 y4b ff3 fs2 fc1 sc0 ls0 ws0">品<span class="_ _0"></span>的<span class="_ _15"></span>问<span class="_ _0"></span>题<span class="_ _15"></span>时<span class="_ _0"></span>候<span class="_ _15"></span>，<span class="_ _0"></span>都<span class="_ _15"></span>有<span class="_ _0"></span>义<span class="_ _15"></span>务<span class="_ _0"></span>把<span class="_ _15"></span>这<span class="_ _0"></span>个<span class="_ _15"></span>问<span class="_ _0"></span>题<span class="_ _0"></span>告<span class="_ _15"></span>知<span class="_ _0"></span>负<span class="_ _15"></span>责<span class="_ _0"></span>这<span class="_ _15"></span>个<span class="_ _0"></span>模<span class="_ _15"></span>块<span class="_ _0"></span>的<span class="_ _15"></span>测<span class="_ _0"></span>试<span class="_ _0"></span>人<span class="_ _15"></span>员<span class="_ _0"></span>去<span class="_ _15"></span>记<span class="_ _0"></span>录<span class="_ _15"></span>跟<span class="_ _0"></span>踪<span class="_ _15"></span>这<span class="_ _0"></span>个</div><div class="t m0 x3 h4 y4c ff1 fs2 fc1 sc0 ls0 ws0">Bug<span class="ff3">，或者干<span class="_ _1"></span>脆自己新建一<span class="_ _1"></span>个<span class="_ _3"> </span><span class="ff1">Bug<span class="_"> </span></span>来跟踪</span></div><div class="t m0 x2 h8 y4d ff4 fs2 fc1 sc0 ls0 ws0">u<span class="_ _e"> </span><span class="ff3">你可以创建一<span class="_ _1"></span>个<span class="_ _2"> </span><span class="ff1">Bug<span class="_ _4"> </span></span>指派给自己，以<span class="_ _1"></span>跟踪某件事的<span class="_ _1"></span>处理。比如开发<span class="_ _1"></span>人员把源代码中<span class="_ _1"></span>的</span></div><div class="t m0 x3 h4 y4e ff3 fs2 fc1 sc0 ls0 ws0">某处问题用<span class="_ _10"> </span><span class="ff1">Bug<span class="_"> </span></span>记录下来<span class="_ _1"></span>，以后抽出时间<span class="_ _1"></span>来进行处理</div><div class="t m0 x2 h8 y4f ff4 fs2 fc1 sc0 ls0 ws0">u<span class="_ _e"> </span><span class="ff3">团队中的所有人<span class="_ _1"></span>都可以创建、指<span class="_ _1"></span>派和更改<span class="_ _10"> </span><span class="ff1">Bug<span class="_"> </span></span>的状态</span></div><a class="l" rel='nofollow' onclick='return false;'><div class="d m1"></div></a></div><div class="pi" data-data='{"ctm":[1.611850,0.000000,0.000000,1.611850,0.000000,0.000000]}'></div></div>
