Sha256: ea1584f3483c28675c6a2140735a8fa801af8b93aaaba79d64b64eba4ed1d59c
Contents?: true
Size: 1.64 KB
Versions: 31
Compression:
Stored size: 1.64 KB
Contents
Feature: request spec
Request specs provide a thin wrapper around Rails' integration tests, and are
designed to drive behavior through the full stack, including routing
(provided by Rails) and without stubbing (that's up to you).
With request specs, you can:
* specify a single request
* specify multiple requests across multiple controllers
* specify multiple requests across multiple sessions
Check the rails documentation on integration tests for more information.
RSpec provides two matchers that delegate to Rails assertions:
render_template # delegates to assert_template
redirect_to # delegates to assert_redirected_to
Check the Rails docs for details on these methods as well.
If you would like to use webrat or capybara with your request specs, all you
have to do is include one of them in your Gemfile and RSpec will
automatically load them in a request spec.
Scenario: specify managing a Widget with Rails integration methods
Given a file named "spec/requests/widget_management_spec.rb" with:
"""
require "spec_helper"
describe "Widget management" do
it "creates a Widget and redirects to the Widget's page" do
get "/widgets/new"
response.should render_template(:new)
post "/widgets", :widget => {:name => "My Widget"}
response.should redirect_to(assigns(:widget))
follow_redirect!
response.should render_template(:show)
response.body.should include("Widget was successfully created.")
end
end
"""
When I run `rspec spec/requests/widget_management_spec.rb`
Then the example should pass
Version data entries
31 entries across 26 versions & 4 rubygems