Chapter21测试驱动的开发与重构(阅读).pptVIP

Easy refactoring Using mock objects as a refactoring technique Easy refactoring Using mock objects as a refactoring technique Inversion of Control(IoC) Applying the IoC pattern to a class means removing the creation of all object instances for which this class is not directly responsible and passing any needed instances instead. Design patterns in action Some people used to say that unit tests should be totally transparant to your code under test, and that you should not change runtime code in order to simplify testing. This is wrong. Unit tests are first-class users of the runtime code and deserve the same consideration as any other user. Using mock objects as a refactoring technique The biggest advantage of the mock-object approach is that it does not require a running container in order to execute the tests The drawbacks of using mock objects are: Do not test interactions with the container or between the components Do not test the deployment part of the components Need excellent knowledge of the API being called in order to mock it, which can be difficult Pros and cons of mock objects SpellChecker例 实现一个拼写检查的组件 该组件能够扩展为对不同类型的输入进行拼写检查，如文本文件，HTML文件等 该组件能够扩展为支持不同类型的语言. 重构(refactoring) 在不改变软件外部行为的前提下，对其内部结构进行改变，使之更容易理解并便于修改。 重构(Refactoring)一词源于Larry Constantine在结构化程序设计中首次使用的‘Factoring’，当时指的是尽可能地将一个程序分解为多个组成部分。 重构与软件的演化： 软件演化的过程是不仅仅是功能的不断完善，而且包括内在的质量不断提高，而内在质量的提高又成为软件进一步演化的基础。 一些常见的需要重构的理由 引用自《代码大全》 代码重复 子程序太长 循环太长或者嵌套太深 类的内聚性太差 某个类与其他类的关系过于密切(耦合过高) 过于依赖基本数据类型 程序中的代码似乎是在将来的某个时候才会用到 重构 重构 描述 提炼方法 将较长的方法转换为短小的方法，其中将原有方法中的部分内容分解为私有的帮助者方法 提炼常量 使用常量变量替换字面常量 引入解释变量 将表达式的部分或者完整结果置入临时变量，该变量的名字应该能够说明其目的 使用工厂方法代替构造函数的调用 使用工厂模式来创建对象，以便隐藏实现细节 重构的例子 public boolean isLeepYear1(int year) { return (year % 400) == 0 || ((year % 4 == 0) (year % 100 != 0)); } public boolean isLeepYear2(int year) { boolean isForthYear = (year % 4 == 0); boolean isHundrethYear = (year % 100 == 0); boolean is4HundrethYear = ((year % 400) == 0); return is4HundrethYear || (isForthYear !isHundrethY