<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Proxying Your Stubs Can Save Space and Time</title>
	<atom:link href="http://gprussell.net/blog/2008/12/25/proxying-your-stubs/feed/" rel="self" type="application/rss+xml" />
	<link>http://gprussell.net/blog/2008/12/25/proxying-your-stubs/</link>
	<description>Occasional articles from the fascinating world of Java (or anywhere else, really)</description>
	<lastBuildDate>Wed, 24 Mar 2010 18:28:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Oleg Zhurakousky</title>
		<link>http://gprussell.net/blog/2008/12/25/proxying-your-stubs/comment-page-1/#comment-5</link>
		<dc:creator>Oleg Zhurakousky</dc:creator>
		<pubDate>Sun, 28 Dec 2008 04:14:04 +0000</pubDate>
		<guid isPermaLink="false">http://gprussell.net/blog/?p=42#comment-5</guid>
		<description>One of the benefits of Stubs over Mocks is reusability, where one can reuse the object (CUT) in other test cases. 
One of the benefits of Mocks over Stubs is dynamics, where one can define a behaviour in-line and see that it is executed.
Both cover the two sides of testing. . . but what is in between???
What if I want to stub one part of a component, but mock the other? This sample clearly shows how it could be accomplished. I almost want to call it reversed AOP Introduction, where arbitrary class (CUT) could be matched to a method or two of the interface view Proxy. . . 
I think a better example would clear up any uncertainty, but pretty clever (I think) from the technology perspective...
Oleg</description>
		<content:encoded><![CDATA[<p>One of the benefits of Stubs over Mocks is reusability, where one can reuse the object (CUT) in other test cases.<br />
One of the benefits of Mocks over Stubs is dynamics, where one can define a behaviour in-line and see that it is executed.<br />
Both cover the two sides of testing. . . but what is in between???<br />
What if I want to stub one part of a component, but mock the other? This sample clearly shows how it could be accomplished. I almost want to call it reversed AOP Introduction, where arbitrary class (CUT) could be matched to a method or two of the interface view Proxy. . .<br />
I think a better example would clear up any uncertainty, but pretty clever (I think) from the technology perspective&#8230;<br />
Oleg</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary P. Russell</title>
		<link>http://gprussell.net/blog/2008/12/25/proxying-your-stubs/comment-page-1/#comment-4</link>
		<dc:creator>Gary P. Russell</dc:creator>
		<pubDate>Sat, 27 Dec 2008 01:46:32 +0000</pubDate>
		<guid isPermaLink="false">http://gprussell.net/blog/?p=42#comment-4</guid>
		<description>&gt;&gt;
You’ve essentially just written a really clumsy implementation of a mock object. 
&lt; &lt;

Thanks for your opinion.

I tried to preempt such comments with my preamble; I guess I failed.
 
&gt;&gt;&gt;
Setting aside the discussion of stubs Vs. mocks in JUnit testing (that is covered more than adequately elsewhere), let’s say you’ve decided to use stubs, for whatever reason.

    Please understand that the simple examples in this article may be more appropriately handled with mocks; they are for illustrative purposes only
&lt;&lt;&lt;

The key phrase being &quot;...let’s say you’ve decided to use stubs, for whatever reason...&quot;

I necessarily had to greatly simplify the example. I had, and have, no intention of getting into a religious war on the subject.</description>
		<content:encoded><![CDATA[<p>>><br />
You’ve essentially just written a really clumsy implementation of a mock object.<br />
< <</p>
<p>Thanks for your opinion.</p>
<p>I tried to preempt such comments with my preamble; I guess I failed.</p>
<p>>>><br />
Setting aside the discussion of stubs Vs. mocks in JUnit testing (that is covered more than adequately elsewhere), let’s say you’ve decided to use stubs, for whatever reason.</p>
<p>    Please understand that the simple examples in this article may be more appropriately handled with mocks; they are for illustrative purposes only<br />
<<<</p>
<p>The key phrase being &#8220;&#8230;let’s say you’ve decided to use stubs, for whatever reason&#8230;&#8221;</p>
<p>I necessarily had to greatly simplify the example. I had, and have, no intention of getting into a religious war on the subject.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles Miller</title>
		<link>http://gprussell.net/blog/2008/12/25/proxying-your-stubs/comment-page-1/#comment-3</link>
		<dc:creator>Charles Miller</dc:creator>
		<pubDate>Fri, 26 Dec 2008 21:20:26 +0000</pubDate>
		<guid isPermaLink="false">http://gprussell.net/blog/?p=42#comment-3</guid>
		<description>You&#039;ve essentially just written a really clumsy implementation of a mock object. Why not go the whole hog at this point and use a real mock framework that&#039;s actually better designed, easier to use and expresses the intent of the test more clearly?</description>
		<content:encoded><![CDATA[<p>You&#8217;ve essentially just written a really clumsy implementation of a mock object. Why not go the whole hog at this point and use a real mock framework that&#8217;s actually better designed, easier to use and expresses the intent of the test more clearly?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom McCuch</title>
		<link>http://gprussell.net/blog/2008/12/25/proxying-your-stubs/comment-page-1/#comment-2</link>
		<dc:creator>Tom McCuch</dc:creator>
		<pubDate>Thu, 25 Dec 2008 23:09:34 +0000</pubDate>
		<guid isPermaLink="false">http://gprussell.net/blog/?p=42#comment-2</guid>
		<description>This is especially nice for consulting engagements where the consultant is being brought in to implement a few bug fixes and/or some additional functionality to an existing system and needs to verify the new development was completed as designed with pin-point precision, and without breaking the bank.</description>
		<content:encoded><![CDATA[<p>This is especially nice for consulting engagements where the consultant is being brought in to implement a few bug fixes and/or some additional functionality to an existing system and needs to verify the new development was completed as designed with pin-point precision, and without breaking the bank.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
