<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: rspec on rails, LocalJumpError - no block given</title>
	<link>http://matt-beedle.com/2007/09/24/rspec-on-rails-localjumperror-no-block-given/</link>
	<description></description>
	<pubDate>Sat, 05 Jul 2008 00:30:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2</generator>

	<item>
		<title>By: matt</title>
		<link>http://matt-beedle.com/2007/09/24/rspec-on-rails-localjumperror-no-block-given/#comment-6631</link>
		<author>matt</author>
		<pubDate>Sun, 29 Jun 2008 09:06:13 +0000</pubDate>
		<guid>http://matt-beedle.com/2007/09/24/rspec-on-rails-localjumperror-no-block-given/#comment-6631</guid>
		<description>Hi Brit,

Since the introduction of foxy fixtures in Rails 2.0 I have actually reverted to using fixtures.  I have had quite a few problems using mocks/stubs because imho they result in brittle tests.  Here's an example using TestUnit http://szeryf.wordpress.com/2008/01/07/does-stubbing-make-your-tests-brittle/ but the same applies to rspec.  Generally, I will only use mocks now when I need to test my applications interaction with an external library, or something where the implementation is fixed.  Maybe I'll write a separate post on this sometime.</description>
		<content:encoded><![CDATA[<p>Hi Brit,</p>
<p>Since the introduction of foxy fixtures in Rails 2.0 I have actually reverted to using fixtures.  I have had quite a few problems using mocks/stubs because imho they result in brittle tests.  Here&#8217;s an example using TestUnit <a href="http://szeryf.wordpress.com/2008/01/07/does-stubbing-make-your-tests-brittle/" rel="nofollow">http://szeryf.wordpress.com/2008/01/07/does-stubbing-make-your-tests-brittle/</a> but the same applies to rspec.  Generally, I will only use mocks now when I need to test my applications interaction with an external library, or something where the implementation is fixed.  Maybe I&#8217;ll write a separate post on this sometime.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Britt</title>
		<link>http://matt-beedle.com/2007/09/24/rspec-on-rails-localjumperror-no-block-given/#comment-6623</link>
		<author>Britt</author>
		<pubDate>Sun, 29 Jun 2008 01:14:15 +0000</pubDate>
		<guid>http://matt-beedle.com/2007/09/24/rspec-on-rails-localjumperror-no-block-given/#comment-6623</guid>
		<description>Hi Matt,

Have you found any better way to organize this kind of speccing?
I am going through the same pains as you and have begun to go down the road of nested describe sequences... but it still requires me to mock EVERYTHING at the first before(:each) declaration.  I would like to incrementally mock/stub as i begin working down through my code and nested describe blocks</description>
		<content:encoded><![CDATA[<p>Hi Matt,</p>
<p>Have you found any better way to organize this kind of speccing?<br />
I am going through the same pains as you and have begun to go down the road of nested describe sequences&#8230; but it still requires me to mock EVERYTHING at the first before(:each) declaration.  I would like to incrementally mock/stub as i begin working down through my code and nested describe blocks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ivor</title>
		<link>http://matt-beedle.com/2007/09/24/rspec-on-rails-localjumperror-no-block-given/#comment-4719</link>
		<author>Ivor</author>
		<pubDate>Tue, 20 May 2008 19:27:54 +0000</pubDate>
		<guid>http://matt-beedle.com/2007/09/24/rspec-on-rails-localjumperror-no-block-given/#comment-4719</guid>
		<description>Thanks!</description>
		<content:encoded><![CDATA[<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: matt</title>
		<link>http://matt-beedle.com/2007/09/24/rspec-on-rails-localjumperror-no-block-given/#comment-3884</link>
		<author>matt</author>
		<pubDate>Wed, 02 Apr 2008 14:49:22 +0000</pubDate>
		<guid>http://matt-beedle.com/2007/09/24/rspec-on-rails-localjumperror-no-block-given/#comment-3884</guid>
		<description>Glad I could help Clemens.  Just took a look at http://tupalo.com/ and I love it!  Looks like a much nicer and more modern version of a site I used to work for called upmystreet.com.</description>
		<content:encoded><![CDATA[<p>Glad I could help Clemens.  Just took a look at <a href="http://tupalo.com/" rel="nofollow">http://tupalo.com/</a> and I love it!  Looks like a much nicer and more modern version of a site I used to work for called upmystreet.com.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clemens</title>
		<link>http://matt-beedle.com/2007/09/24/rspec-on-rails-localjumperror-no-block-given/#comment-3883</link>
		<author>Clemens</author>
		<pubDate>Wed, 02 Apr 2008 14:38:50 +0000</pubDate>
		<guid>http://matt-beedle.com/2007/09/24/rspec-on-rails-localjumperror-no-block-given/#comment-3883</guid>
		<description>Thanks - had exactly the same problem. Your post cleared that up.</description>
		<content:encoded><![CDATA[<p>Thanks - had exactly the same problem. Your post cleared that up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GadgetGadget.info - Gadgets on the web &#187; rspec on rails, LocalJumpError - no block given</title>
		<link>http://matt-beedle.com/2007/09/24/rspec-on-rails-localjumperror-no-block-given/#comment-1804</link>
		<author>GadgetGadget.info - Gadgets on the web &#187; rspec on rails, LocalJumpError - no block given</author>
		<pubDate>Mon, 24 Sep 2007 17:10:21 +0000</pubDate>
		<guid>http://matt-beedle.com/2007/09/24/rspec-on-rails-localjumperror-no-block-given/#comment-1804</guid>
		<description>[...] unknown wrote an interesting post today!.Here&#8217;s a quick excerptIn the rails code, ActiveRecord::Base::find is being called which is really doing a scoped find for all photos belonging to the user. The solution is to stub the find method on the photos array in the before block of your rspec tests. &#8230; [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] unknown wrote an interesting post today!.Here&#8217;s a quick excerptIn the rails code, ActiveRecord::Base::find is being called which is really doing a scoped find for all photos belonging to the user. The solution is to stub the find method on the photos array in the before block of your rspec tests. &#8230; [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
