Comments on: Where does that Python DB handle go? http://www.protocolostomy.com/2007/07/21/python-database-handle/ Made with only the finest 1's and 0's Thu, 26 Jan 2012 21:20:45 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: m0j0 http://www.protocolostomy.com/2007/07/21/python-database-handle/comment-page-1/#comment-134 m0j0 Sun, 22 Jul 2007 20:33:11 +0000 http://bkj.protocolostomy.com/?p=227#comment-134 rrenaud - you're absolutely right. This is another aspect of the application that I had not considered (in addition to Brend's input, which is in the UPDATE above). Thanks a lot for pointing this out. rrenaud – you’re absolutely right. This is another aspect of the application that I had not considered (in addition to Brend’s input, which is in the UPDATE above). Thanks a lot for pointing this out.

]]> By: rrenaud http://www.protocolostomy.com/2007/07/21/python-database-handle/comment-page-1/#comment-135 rrenaud Sun, 22 Jul 2007 18:24:21 +0000 http://bkj.protocolostomy.com/?p=227#comment-135 I think (3) is the wrong decision from a software engineering/test driven design point of view. How can you write a unittest for your Host class? Presumably, inside Host.init() it knows how to connect to the in production database. You don't want a unittest run to have any real world side effects. If you pass in the handle to your Host class, you could presumably replace the database connection with a mock object (or maybe an SQL-lite handle for a database created on the fly for the unittest) so that you can test your class side effect free. Google for test driven design and mock objects if you want the gory details. I think (3) is the wrong decision from a software engineering/test driven design point of view. How can you write a unittest for your Host class? Presumably, inside Host.init() it knows how to connect to the in production database. You don’t want a unittest run to have any real world side effects. If you pass in the handle to your Host class, you could presumably replace the database connection with a mock object (or maybe an SQL-lite handle for a database created on the fly for the unittest) so that you can test your class side effect free.

Google for test driven design and mock objects if you want the gory details.

]]>