Trouble with Mocking

I'm using some ideas from Beast to load all fixtures, and I do find that it slows things down. I don't mind waiting an extra second or two for tests to run, though, and it's better than having tests fail because you're missing fixtures.

I hear that you can speed up testing by doing it with SQLite, and wasn't Geoffrey Grosenbach doing something where you can run tests in memory?

I hate fixtures just as much as the next guy, but if you keep them up to date (TDD, test-first) then it's not so bad. I don't know what the alternative would be, honestly.

Cool. I'm checking out the changelog here:

http://dev.rubyonrails.org/changeset/6227

... and it looks like this is the default behavior now. Nice!

It might look something like this:

describe ItemsController do
  fixtures :all
  integrate_views
  
  it "index action should render index template" do
    get 'index'
    response.should render_template(:index)
  end
  
  it "show action should render show template" do
    get 'show', :id => 1
    response.should render_template(:show)
  end
  
  it "new action should render new template" do
    get 'new'
    response.should render_template(:new)
  end
  
  it "create action should render new template when model is invalid" do
    item = Item.new
    item.stub!(:valid?).and_return(false)
    @controller.stub!(:fetch_model).and_return(item)
    post 'create'
    response.should render_template(:new)
  end
  
  it "create action should redirect to index action when model is valid" do
    item = Item.new
    item.stub!(:valid?).and_return(true)
    @controller.stub!(:fetch_model).and_return(item)
    post 'create'
    response.should redirect_to(items_path)
  end
  
  it "edit action should render edit template" do
    get 'edit', :id => 1
    response.should render_template(:edit)
  end
  
  it "update action should render edit template when model is invalid" do
    item = Item.find(1)
    item.stub!(:valid?).and_return(false)
    @controller.stub!(:fetch_model).and_return(item)
    put 'update', :id => 1
    response.should render_template(:edit)
  end
  
  it "update action should redirect to show action when model is valid" do
    item = Item.find(1)
    item.stub!(:valid?).and_return(true)
    @controller.stub!(:fetch_model).and_return(item)
    put 'update', :id => 1
    response.should redirect_to(item_path(item))
  end
  
  it "destroy action should destroy item and redirect to index action" do
    delete 'destroy', :id => 1
    response.should redirect_to(items_path)
    Item.find_by_id(1).should be_nil
  end
end

This won't quite work with scaffold_resource because it relies on there being a method in the controller called "fetch_model" which returns the model. I stub this out sometimes so I can return whatever model I want in the test.

Also, there's quite a bit of duplication here, I refactored this out into a module so it's easier to test these 7 actions.

still rspec nuby:
Thanks for bringing up the issue what I have as well. Moreover I'm holding dev and test data in the same fixtures (so I can reset everything easily, just haven't think out better place for dev data). Therefore fixtures holds only "good" data and everything else I plan to stub/mock out.

Don't know if it's good way yet but let's see what practice will bring.