软件测试培训之软件缺陷的优先级

软件测试培训之软件缺陷的优先级

(1)优先级0(Priority 0)

问题导致了中断或者阻止了产品的正常版本编译(Issues that break or prevent a product build)

问题导致了阻止了BVT和其他测试自动化的运行(Issues that prevent BVTs and other test automation)

问题导致了无法成功构建国内和全球文档(Issues that keep production from successfully building Domestic and International Doc Builds)

由于粗心丢失内容，如文档文件、命名空间(Unintentionally dropped out content, e.g. doc file, namespace)

(2)优先级1(Priority 1)

这类软件缺陷必须修复然后才能发布产品或者才能达到用户体验所包含的最主要目标(Bugs that must be fixed in order to ship the product or achieve UE's top/main goals)：

高法律风险;地域相关;版权，商标，准许法令(High Legal risk; Geopolitical, Copyright, Trademark, Consent Decree)

高风险编码实践(High risk security coding practices)

对用户/产品关键的用于描述场景的新文档和/或新特性(New documentation for scenarios and/or new features that are crucial to customers and/or the product)

辅助访问主题的元数据的变更;搜索，属性F1和索引问题(Metadata changes to help access topics; search, attributes, F1 and indexing issues)

在目标命名空间中的代码样例/代码片段(Code samples/snippets in targeted namespaces)

过多从参考文档到概念性文档的引用(More linking of reference docs to conceptual docs )

在顶层页面/节点发现的问题，例如在首页，门户上发现的问题(Issue found on top level pages/node,e.g., homepage, portal)

在大标题上存在的问题(Issue appears in a large number of topics through out the doc set)

技术性的不正确的内容(Technically incorrect content)

(3)优先级2(Priority 2)

软件缺陷应该被修复(Bugs that should be fixed)：

对客户和产品不是那么关键性的场景或者特性(Scenarios or features that are not crucial to customers or the product)

从先前版本来的内容修复(Fixing content from previous releases)

非目标命名空间中代码样例/代码片段(Code samples/snippets in non targeted namespaces)

在中等级页面/节点中发现的缺陷(Bug found in mid level pages/nodes)

在小标题上存在的问题(Bug appears in a significant number of topics through out the doc set)

(4)优先级3(Priority 3)

如果修复这个缺陷会比较好(Bugs that would be good to fix)：

目录问题(Table of Contents issues)

重写或重新格式化原本正确的文档，为了让它更清晰，更容易阅读(Rewriting or reformatting correct content to make it clearer, easier to read)

在视觉上影响到用户但是但不影响阅读(Issues that visually impacts the customer but won't affect the readability or use of the topic)

最佳实践修复(Best practice fixes)

代码样例/代码片段(Code samples/snippets)

在低级的页面中/节点中发现的问题(Issues found in low level pages/nodes)

被阅读很少的主题(Issues found in a small number of topics)

(5)优先级4(Priority 4)

如果修复这个缺陷我们的工作就算是达到精细的程度，这种问题比较细小，可以被推迟处理(Bugs that would be nice to fix, are trivial and can be postponed)：

在文档中藏得比较深的问题(Issues buried in the docs)

仅在一个话题中有的问题(Issues found in only one topic )

对用户影响比较小的问题(Issues with low to no customer impact)

如果要修复这个问题导致的本地化的投入要比对用户的获益高得多(Issues with a high localization cost versus customer gain