Awesome. I totally get it, but is that how you're always supposed to spec out associations and all the methods that go with an association like "create" and such? I'm interested in that because I'm specing a lot of code that deals heavily with code that has associations going on, yet none of the examples of RSpec use I come across have anything about associations and RSpec. I don't imagine they'd be handled too differently, but it's just something wondered about. <br>
<br>Right now, I'm testing and building up a controller and so far my tests have been passing as long as I don't run into any examples that involve associations. This code, for example, has been giving me a few issues:<br>
<br># my users_controller_spec.rb (or at least, the relevant part)<br><br><div>describe UsersController do</div><div> fixtures :users</div><div> </div><div> before(:each) do</div><div> @tiffani = users(:tiffani)</div>
<div> @users = [@tiffani]</div><div> @users.stub!(:build).and_return(@tiffani)</div><div> @mock_account = mock_model(Account, :users => @users, :save => true)</div><div> end</div><div> </div><div> describe "when creating a User" do</div>
<div> it "should return the registration form for adding a User on GET new" do</div><div> User.should_receive(:new).once</div><div> get :new</div><div> end</div><div> </div><div> it "should render the new User registration form on GET new" do</div>
<div> get :new</div><div> response.should render_template("users/new")</div><div> end</div><div> </div><div> it "should create a new User and then redirect to that User's profile on POST create" do</div>
<div> @mock_account.should_receive(:new)</div><div> post :create, :new_user => { :first_name => @tiffani.first_name, :last_name => @tiffani.last_name,</div><div> :email_address => @tiffani.email_address }</div>
<div> end</div><div> </div><div> it "should redirect to users/new when User is setup with invalid data"</div><div> end<br><br> # ...<br>end<br><br>And in users_controller.rb:<br><br><div>def create</div>
<div> @new_account = Account.new(params[:account])</div><div> @new_user = @new_account.users.build(params[:new_user])</div><div> </div><div> respond_to do |wants|</div><div> if @new_account.save</div><div>
flash[:notice] = "Welcome, #{ @new_user.first_name }!"</div><div> wants.html { redirect_to(user_url(@new_user)) }</div><div> else</div><div> wants.html { render :action => "new" }</div>
<div> end</div><div> end</div><div> end<br></div></div><br><br>When I run the tests the third test fails and RSpec complains that "<span class="Apple-style-span" style="color: rgb(194, 0, 0); font-family: -webkit-monospace; font-size: 11px; white-space: pre; ">Mock 'Account_1003' expected :new with (any args) once, but received it 0 times"<br>
<br></span>I'm confused about that since I am calling Account.new in the create method on the controller. What's really wrong here?<br><br>Thanks in advance for answering my RSpec questions! :D<br><br>--Tiffani AB<br>
<br><br><div class="gmail_quote">On Thu, Jul 3, 2008 at 9:09 PM, Mikel Lindsaar <<a href="mailto:raasdnil@gmail.com">raasdnil@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
On Fri, Jul 4, 2008 at 8:32 AM, Tiffani Ashley Bell<br>
<<a href="mailto:tiffani2k3@gmail.com">tiffani2k3@gmail.com</a>> wrote:<br>
> Hi everybody,<br>
<br>
Hi Tiffany, welcome to Rspec<br>
<div class="Ih2E3d"><br>
> I was reading the Typo source code, however, and came across some code that<br>
> I didn't know exactly how it worked. I've noticed that in testing one of<br>
> their controllers, they use a variable (@comments) that they don't declare<br>
> anywhere else, yet they use it as a stand in for collections on some of the<br>
> mocks. How is that possible? I know in the mocking documentation it says<br>
> that you can define collaborations with other objects before those objects<br>
> exist, but how is that working in this code? I only ask that because later,<br>
> you see code like this: @comments.stub!(:build).and_return(@comment).<br>
<br>
</div>If you have a look at the descriptions, they use :shared => true.<br>
This is a way of being DRY in RSpec (which I personally don't think is<br>
such a good idea).<br>
<br>
What the shared => true declaration allows you to do is to include<br>
that block of code elsewhere with 'it should behave like my shared<br>
code'<br>
<br>
So we have (describe "All Requests", :shared => true do)<br>
<br>
and then the next description block is:<br>
<br>
describe "General Comment Creation", :shared => true do<br>
it_should_behave_like "All Requests"<br>
<br>
Which then includes the All Requests block (which is just a before method).<br>
<br>
The @comments variable gets declared in:<br>
<div class="Ih2E3d"><br>
@comments.stub!(:build).and_return(@comment)<br>
<br>
</div>and then this is tied in to the Article model in the _previous_ code<br>
block like so:<br>
<br>
@article = mock_model(Article,<br>
:comments => @comments,<br>
:published_comments => @comments,<br>
:add_comment => @comment)<br>
<br>
<br>
So when you call @article.comments you get @comments as a stub back<br>
which stubs :build and returns a @comment.<br>
<br>
Ugh.<br>
<br>
This is where, in RSpec, you can dig a very fast grave. Because<br>
you'll come back to this code in 6-12 months and be totally stuck<br>
trying to figure out what is where.<br>
<br>
I recently wrote a viewpoint on this that might help you:<br>
<a href="http://www.lindsaar.net/2008/6/24/tip-24-being-clever-in-specs-is-for-dummies" target="_blank">http://www.lindsaar.net/2008/6/24/tip-24-being-clever-in-specs-is-for-dummies</a><br>
<br>
Hope you do well with Rspec, feel free to ask more questions!<br>
<font color="#888888"><br>
--<br>
<a href="http://lindsaar.net/" target="_blank">http://lindsaar.net/</a><br>
Rails, RSpec, Puppet and Life blog....<br>
_______________________________________________<br>
rspec-users mailing list<br>
<a href="mailto:rspec-users@rubyforge.org">rspec-users@rubyforge.org</a><br>
<a href="http://rubyforge.org/mailman/listinfo/rspec-users" target="_blank">http://rubyforge.org/mailman/listinfo/rspec-users</a><br>
</font></blockquote></div><br>