T3.静态测试教程.ppt

* 基于圈复杂度的风险分析 圈复杂度 与之联系的风险 1 ~ 10 低风险的简单程序 11 ~ 20 中等的复杂度和风险 21 ~ 50 高复杂度和风险 50+ 非常高的风险/不可测试 原子条件 原子条件指条件中不包含与、或、非运算的条件 画控制流图时注意 当程序中判定条件为复合条件时应将复合条件分解成原子条件后，再画出控制流图，进行圈复杂度计算 例： * 随堂练习 为以下代码画出控制流图，并计算圈复杂度 void Method(bool condition) { if (condition) { Console.WriteLine(Hello World!); } } * 随堂练习 为以下代码画出控制流图，并计算圈复杂度 void CycleSampleTwo(int value) { if (value != 0) { if (value 0) value += 1; else { if (value == 999) //special value value = 0; else value -= 1; } } } * 随堂练习 计算以下控制流图的圈复杂度 有点难度的练习 要求： 画出右面代码的控制流图，并计算圈复杂度 * 课后练习 以组委单位，查询资料，解释等价类划分法是如何设计测试用例的，描述其步骤。 * Do stated goals and objectives for software remain consistent with system goals and objectives? Have important interfaces to all system elements been described? Have all data objects been described? Have all attributes been identified? Do major functions remain within scope and has each been adequately described? Have functions been refined (elaborated) to an appropriate level of detail? Is information flow adequately defined for the problem domain? Are diagrams clear; can each stand alone without supplementary text? Is the behavior of the software consistent with the information it must process and the functions it must perform? Have events and states been identified? Are design constraints realistic? Have technological risks been fully defined? Have alternative software requirements been considered? Have validation criteria been stated in detail; are they adequate to describe a successful system? Have inconsistencies, omissions or redundancy been identified and corrected? Is the customer contact complete? Has the user reviewed the Preliminary Users Manual or prototype? How are the Software Project Plan estimates affected? * 2.4 评审的类型 主要的评审类型有以下几种： 非正式评审（informal review） 技术评审（technical review） 走查（walkthrough） 审查（inspection） * 非正式评审（informal review） 非正式的过程 结果不需要明确的文档化 其效果因评审员的不同而异 工作量、成本最小 结对编程、结对测试、代码交换等都是非正式评审的方式 * 技术评审（technical r