- controller - helper - mailer - request - routing - view This supports attaching behaviour to a subset of example groups in a config block: RSpec.configure do |c| before(:each, :type => :controller) do # do something end end Note that this is not mean you can attach controller spec behaviour to a group like this: # DOES NOT WORK describe "something", :type => :controller do Closes #38.
from the top of the Rakefile that was there in case RSpec wasn't installed. Closes #122.
gemset (with no previous versions of rspec around) for this all to work. Period.
bundler-1.0.0.beta.2, but does work with bundler built from commit b078098212de02f1505b4c73de0a2e8e68ee3d65, and therefore will hopefully work with bundler-1.0.0.beta.3, which is due out any day).
happens unless RSpec is installed.
away. Closes #123.
…nerating a" This reverts commit 12f0afa. - Rails controller generator does not generate the routes needed for the generated request spec. Backing this out.
controller or resource. Closes #33.
place. Closes #116.
- There is really no benefit from the attribute/non-attribute distinction when setting stubs. - This helps to make stub_model usable with non-ActiveRecord models Closes #108.
Because templates cache their content when rendered, modifying the template source only works if the template had not yet been rendered. - added a cucumber scenario with several example groups alternately using render_views and not, to show that the rendered templates are not cached across requests - NOTE that this does not mean templates are not cached internally in Rails. Just that the templates used in controller specs are not the same ones cached by Rails (though they are initialized with all of the same data).