@steveklabnik Lots of little functions: https://github.com/whit537/aspen/blob/0dacfff55b3b258cac09a99bd86abaf64eaf1e07/tests/test_gauntlet.py …. Lots of bloated classes: https://github.com/whit537/www.gittip.com/blob/78b7f5f6b109cf9235aaf183249155852a4919dd/tests/test_billing.py …. /cc @marshall_jones
-
-
Replying to @chadwhitacre_
@whit537 yeah so if you don’t actually use mocks to drive your design, it can get real awkward1 reply 0 retweets 0 likes -
Replying to @steveklabnik
@steveklabnik Hmmm ... new thought for me. Will have to chew on it.2 replies 0 retweets 0 likes -
Replying to @chadwhitacre_
@whit537 also, you should only mock things you own… but yes, mocks are a design tool, not a testing tool. tons of literature on this.1 reply 0 retweets 0 likes -
Replying to @steveklabnik
@steveklabnik What do I do with things I don't own? E.g.,@balancedpayment's client library features prominently in Gittip's test suite.1 reply 0 retweets 0 likes
Replying to @chadwhitacre_
@whit537 you wrap them, integration test the wrappers
4:22 PM - 23 Aug 2012
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.