Comments on: TDD: How to supersede a single system library call http://richarddingwall.name/2009/05/09/tdd-how-to-supersede-a-single-system-library-call/ The adventures of a young kiwi software developer in London Thu, 10 May 2012 16:20:46 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Richard http://richarddingwall.name/2009/05/09/tdd-how-to-supersede-a-single-system-library-call/comment-page-1/#comment-4827 Richard Mon, 18 May 2009 10:42:38 +0000 http://richarddingwall.name/?p=1332#comment-4827 @Alex: it is infrastructure to support testing, yes, and it isn't that pretty, so only use these sort of methods sparingly, for difficult situations. I don't think it is too hard to understand for future programmers though (this is something I also worry about a lot). @Alex: it is infrastructure to support testing, yes, and it isn’t that pretty, so only use these sort of methods sparingly, for difficult situations. I don’t think it is too hard to understand for future programmers though (this is something I also worry about a lot).

]]> By: Alex Hoffman http://richarddingwall.name/2009/05/09/tdd-how-to-supersede-a-single-system-library-call/comment-page-1/#comment-4515 Alex Hoffman Mon, 11 May 2009 22:37:45 +0000 http://richarddingwall.name/?p=1332#comment-4515 I think your injecting infrastructure into your code, just to support testing. A dubious practice? Not to mention that you now have code, that smells of the author having a specific intention, which would no longer be apparent to a new programmer maintaining the code 18 months from now. I think your injecting infrastructure into your code, just to support testing. A dubious practice?

Not to mention that you now have code, that smells of the author having a specific intention, which would no longer be apparent to a new programmer maintaining the code 18 months from now.

]]> By: Beau Crawford http://richarddingwall.name/2009/05/09/tdd-how-to-supersede-a-single-system-library-call/comment-page-1/#comment-4501 Beau Crawford Mon, 11 May 2009 14:11:31 +0000 http://richarddingwall.name/?p=1332#comment-4501 I use this approach a lot. You might consider marking the "SupersedeSendAction" method internal and then granting access to internals for your Test assembly using the InternalsVisibleTo attribute. I use this approach a lot. You might consider marking the “SupersedeSendAction” method internal and then granting access to internals for your Test assembly using the InternalsVisibleTo attribute.

]]>