Tuesday, December 16, 2014
Wednesday, July 18, 2012
Dummy objects are passed around but never actually used. Usually they are just used to fill parameter lists. In Python, None is the ultimate Dummy.
Fake objects actually have working implementations, but usually take some shortcut which makes them not suitable for production (an in memory database is a good example).
Stubs provide canned answers to calls made during the test, usually not responding at all to anything outside what's programmed in for the test. Stubs may also record information about calls, such as an email gateway stub that remembers the messages it 'sent', or maybe only how many messages it 'sent'.
Mocks are objects that are pre-programmed with expectations which form a specification of the calls they are expected to receive.
Lifted from Mocks aren't Stubs and derived from the excellent xUnit patterns book.
Wednesday, February 8, 2012
You wonder how to set a timeout on your HTTP connection?
Try like this:
socket.setdefaulttimeout(3) # 3 seconds
request = urllib2.Request('http://www.yourhost.com')
response = urllib2.urlopen(req)
#urllib2.urlopen will now uses the default timeout of 3 secs.
Thursday, March 3, 2011
Thursday, December 18, 2008
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those! (Tim Peters)