Comments on: Mock objects at CITCON Paris 2009 http://ericlefevre.net/wordpress/2009/09/21/mock-objects-at-citcon-paris-2009/ Eric's Elegant Elucidations Sat, 03 Jul 2010 09:47:02 +0200 http://wordpress.org/?v=2.8.5 hourly 1 By: » CITCON Paris 2009: Mock objects desgrange.net http://ericlefevre.net/wordpress/2009/09/21/mock-objects-at-citcon-paris-2009/comment-page-1/#comment-2952 » CITCON Paris 2009: Mock objects desgrange.net Sat, 01 May 2010 08:25:46 +0000 http://ericlefevre.net/wordpress/?p=743#comment-2952 [...] During the session on mock objects there was a digression about interfaces. I have seen too often interfaces in a way that I don’t like. I will use the same example as Eric: [...] [...] During the session on mock objects there was a digression about interfaces. I have seen too often interfaces in a way that I don’t like. I will use the same example as Eric: [...]

]]> By: CITCON Paris 2009, a personal retrospective of the organization « Eric Lefevre-Ardant on Java & Agile http://ericlefevre.net/wordpress/2009/09/21/mock-objects-at-citcon-paris-2009/comment-page-1/#comment-2881 CITCON Paris 2009, a personal retrospective of the organization « Eric Lefevre-Ardant on Java & Agile Wed, 23 Sep 2009 06:22:02 +0000 http://ericlefevre.net/wordpress/?p=743#comment-2881 [...] from Zutubi… Reconnected with many former colleagues and friends, too. I also attended a few sessions [...] [...] from Zutubi… Reconnected with many former colleagues and friends, too. I also attended a few sessions [...]

]]> By: Steve Freeman http://ericlefevre.net/wordpress/2009/09/21/mock-objects-at-citcon-paris-2009/comment-page-1/#comment-2877 Steve Freeman Tue, 22 Sep 2009 14:10:29 +0000 http://ericlefevre.net/wordpress/?p=743#comment-2877 @Antonio. Fair enough, although an hour (including time spent watching my laptop not work) isn't a lot of time to make a point to a skeptic. There are also other reasons for using interfaces to do with naming, and dependency management I didn't get to. I find that the effect of using interfaces to describe roles only really kicks in as the code scales up. And I'm sure that a good team can make things work with just classes--David's examples looked pretty good to me. In the meantime, I really recommend the Wirfs-Brock book, if you haven't read it yet. It has a long and respectable pedigree. At least we agree on not using the 'I' naming wart. @Antonio. Fair enough, although an hour (including time spent watching my laptop not work) isn’t a lot of time to make a point to a skeptic.

There are also other reasons for using interfaces to do with naming, and dependency management I didn’t get to. I find that the effect of using interfaces to describe roles only really kicks in as the code scales up. And I’m sure that a good team can make things work with just classes–David’s examples looked pretty good to me. In the meantime, I really recommend the Wirfs-Brock book, if you haven’t read it yet. It has a long and respectable pedigree.

At least we agree on not using the ‘I’ naming wart.

]]> By: Faster tests, at CITCON Paris 2009 « Eric Lefevre-Ardant on Java & Agile http://ericlefevre.net/wordpress/2009/09/21/mock-objects-at-citcon-paris-2009/comment-page-1/#comment-2875 Faster tests, at CITCON Paris 2009 « Eric Lefevre-Ardant on Java & Agile Tue, 22 Sep 2009 08:14:27 +0000 http://ericlefevre.net/wordpress/?p=743#comment-2875 [...] check out my notes on the session on Mock Objects. Comments [...] [...] check out my notes on the session on Mock Objects. Comments [...]

]]> By: Antonio Goncalves http://ericlefevre.net/wordpress/2009/09/21/mock-objects-at-citcon-paris-2009/comment-page-1/#comment-2872 Antonio Goncalves Mon, 21 Sep 2009 22:20:42 +0000 http://ericlefevre.net/wordpress/?p=743#comment-2872 For me an interface should be called Serializable, Comparable, FileFilter... when you start using the same name with a prefix ('I' for interface) or a suffix ('Impl' for the implementation), that is a code smell. I don't like the idea of having interfaces when you only have one implementation. The more I code, the less I use interfaces... unless it's needed (for implementation or testing reasons). I was at the talk with Steve but left the room without being conviced at all. For me an interface should be called Serializable, Comparable, FileFilter… when you start using the same name with a prefix (’I’ for interface) or a suffix (’Impl’ for the implementation), that is a code smell. I don’t like the idea of having interfaces when you only have one implementation. The more I code, the less I use interfaces… unless it’s needed (for implementation or testing reasons). I was at the talk with Steve but left the room without being conviced at all.

]]>