Comments on: Partial Mocks explained http://elegantcode.com/2008/04/08/partial-mocks-explained/?utm_source=rss&utm_medium=rss&utm_campaign=partial-mocks-explained Tue, 07 Feb 2012 23:42:00 +0000 hourly 1 http://wordpress.org/?v=3.0.5 By: John http://elegantcode.com/2008/04/08/partial-mocks-explained/comment-page-1/#comment-63862 John Wed, 01 Jun 2011 16:47:00 +0000 http://elegantcode.com/2008/04/08/partial-mocks-explained/#comment-63862 Thanks, good explanation. Thanks, good explanation.

]]> By: Palle Cogburn http://elegantcode.com/2008/04/08/partial-mocks-explained/comment-page-1/#comment-24910 Palle Cogburn Wed, 25 Jun 2008 22:26:00 +0000 http://elegantcode.com/2008/04/08/partial-mocks-explained/#comment-24910 Thank you. This was very helpful to me. I am learning Moq and I was having a problem testing classes that had statements like this: <code>Context.Current.ActiveProcessor.GetInstrument(InstrumentId id)</code> I now realize that the design needs to be changed to be testable to isolate the statement into a separate method. Bottom line is: "If you can't test it, your design is wrong." Thank you. This was very helpful to me. I am learning Moq and I was having a problem testing classes that had statements like this:
Context.Current.ActiveProcessor.GetInstrument(InstrumentId id)

I now realize that the design needs to be changed to be testable to isolate the statement into a separate method.

Bottom line is: “If you can’t test it, your design is wrong.”

]]> By: J-F Pinero http://elegantcode.com/2008/04/08/partial-mocks-explained/comment-page-1/#comment-24052 J-F Pinero Tue, 17 Jun 2008 03:55:16 +0000 http://elegantcode.com/2008/04/08/partial-mocks-explained/#comment-24052 Thanks for the quick comparison. We use Rhino at work (well my small team does) and I've been trying to convince them to switch over to Moq since we started using c# 3.0. This will be a nice little "Hello Moq World" example for them. Thanks for the quick comparison. We use Rhino at work (well my small team does) and I’ve been trying to convince them to switch over to Moq since we started using c# 3.0.

This will be a nice little “Hello Moq World” example for them.

]]> By: Links Today (2008-04-10) http://elegantcode.com/2008/04/08/partial-mocks-explained/comment-page-1/#comment-19645 Links Today (2008-04-10) Thu, 10 Apr 2008 15:32:28 +0000 http://elegantcode.com/2008/04/08/partial-mocks-explained/#comment-19645 [...] Partial Mocks explained [...] [...] Partial Mocks explained [...]

]]> By: Jeff Brown http://elegantcode.com/2008/04/08/partial-mocks-explained/comment-page-1/#comment-19577 Jeff Brown Wed, 09 Apr 2008 09:32:10 +0000 http://elegantcode.com/2008/04/08/partial-mocks-explained/#comment-19577 Argh, I got the wrong website link in there again. FireFox "helpfully" cached it for me from earlier. *sigh* Argh, I got the wrong website link in there again. FireFox “helpfully” cached it for me from earlier. *sigh*

]]> By: Jeff Brown http://elegantcode.com/2008/04/08/partial-mocks-explained/comment-page-1/#comment-19576 Jeff Brown Wed, 09 Apr 2008 09:29:26 +0000 http://elegantcode.com/2008/04/08/partial-mocks-explained/#comment-19576 Looks good! Anyways, don't worry too much about being "schooled." I was actually the one who asked Ayende to add PartialMock in the first place and I contributed a few other things besides. So Rhino.Mocks is pretty dear to my heart. :-) Now Moq is starting to look pretty good with those tidy little lambdas... There's a lot of potential for more expressive syntax with C# 3.0. mmm! Looks good!

Anyways, don’t worry too much about being “schooled.” I was actually the one who asked Ayende to add PartialMock in the first place and I contributed a few other things besides. So Rhino.Mocks is pretty dear to my heart. :-)

Now Moq is starting to look pretty good with those tidy little lambdas… There’s a lot of potential for more expressive syntax with C# 3.0. mmm!

]]>