＋设为首页 ＋添加到收藏夹
introduction
many people have observed that unit testing fits the mold of heisenberg’s uncertainty principle which says, among other things, that at the quantum level, the act of observing an event changes the nature of that event. unit tests often have the same effect, but it extends beyond the runtime event being tested. it affects the design of the code that is to be tested, as well. 【程序编程相关:我的Linux起步】
you know you have to write unit tests. you have the tools, and your team is committed to the idea. somehow, though, despite your best intentions, the tests just never get written. or you write them, but never run them. they always fail anyway. for one reason or another, your project is resisting the will of the unit test. usually, this means that your code needs a good solid refactoring, to make it more accepting of the way of the test. 【推荐阅读:关于linux与windows的共享】
use interfaces 【扩展信息:A few Tips Of Suse】
in this column, we’ll examine ten different ways you can change your code to make it ready to be tested. by doing so, you will be creating a more loosely coupled, flexible and transparent architecture, which will benefit you not only in testing but in documentation, maintenance and, eventually, modification. with a little forethought and some careful implementation, the unit tests can drive more than the qa process; it can help you design a more robust application in the first place.
those of us who came through the com days with our registries intact remember that most strident of admonitions: “it’s the interfaces, stupid”. to write com code, you had to employ interfaces as the primary coupling mechanism. for the un- (or under-)initiated, interfaces are lightweight constructs which define the publicly accessible method signatures exposed by a class; they contain no implementation details whatsoever. instantiated objects can be referred to by references of the interface type, but the interface can never be instantiated itself.
here is a simple interface example: we’ll define an interface for interacting with different kinds of agents. the interface is called iagent:
public interface iagent { string agentname {get; set;} bool accomplishmission(timespan timelimit); }agents all have a name, and can attempt to accomplish a mission in a given amount of time.
we’ll implement two different kinds of agents, secretagents and airlineagents. airline agents perform their mission by getting people on planes, and secret agents have clandestine rendezvous’s. in addition, the secretagent, if in undercover mode, won’t reveal her name.
... 下一页