Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 968589
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T02:30:27+00:00 2026-05-16T02:30:27+00:00

I’ve recently just added Devise to my first Rails3 app, and I’m having a

  • 0

I’ve recently just added Devise to my first Rails3 app, and I’m having a bit of trouble with the controller tests.

I’m testing the User controller class, which is the same model that Devise uses. So at the beginning of my spec I have this:

before(:each) do
  sign_in @user = Factory.create(:user)
end

Now I can get the test passing without using mocking or stubbing like so:

describe "GET edit" do
  it "assigns the requested user as @user" do
    user = Factory(:user)
    get :edit, :id => user.id
    assigns(:user).should eql(user)
  end
end

But for educational purposes I would like to know how to get it to work with mocking and stubbing, normally it would be completely straight forward, but it seems Devise is calling User.find before the controller action, and making the test fail.

describe "GET edit" do
  it "assigns the requested user as @user" do
    user = Factory(:user)
    User.expects(:find).with(:first, :conditions => {:id => 37}).returns(user)
    get :edit, :id => '37'
    assigns(:user).should be(user)
  end
end

Also by adding twice onto the expectation this would also fail because the first call to find is different to the one I’m setting the expectation for.

Any insight would be appreciated.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-16T02:30:27+00:00Added an answer on May 16, 2026 at 2:30 am

    You can specify multiple return values with either stubs or expects like so:

    require 'test/unit'
    require 'mocha'
    
    class Foo
    end
    
    class FooTest < Test::Unit::TestCase
    
      # This passes!
      def test_multiple_returns_with_stubs
        Foo.stubs(:find).returns('a').returns('b').returns('c')
    
        assert_equal('a', Foo.find('z'))
        assert_equal('b', Foo.find('y'))
        assert_equal('c', Foo.find('x'))
      end
    
      # This passes too!
      def test_multiple_returns_with_expects
        Foo.expects(:find).times(1..3).returns('a').returns('b').returns('c')
    
        assert_equal('a', Foo.find('z'))
        assert_equal('b', Foo.find('y'))
        assert_equal('c', Foo.find('x'))
      end
    end
    

    The difference, apparently, is that expects needs to know how many times it’s going to be called. If you don’t specify anything, it assumes once and will complain on the subsequent calls. stubs doesn’t care.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

No related questions found

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.