Sha256: 8c90de2c06a96611aa0ef12449da745a57fd95e0159a13c9960e1a5de251ecbb
Contents?: true
Size: 1.82 KB
Versions: 22
Compression:
Stored size: 1.82 KB
Contents
require File.dirname(__FILE__) + '/../spec_helper'
# These two example groups are specifying the exact same behavior. However, the documentation style is different
# and the value that each one provides is different with various trade-offs. Run these examples with the specdoc
# formatter to get an idea of how they differ.
# Example of documenting the behaviour explicitly and expressing the intent in the example's sentence.
describe "Signup Email" do
include EmailSpec::Helpers
include EmailSpec::Matchers
include ActionController::UrlWriter
default_url_options = {:host => 'example.com'}
before(:all) do
@email = UserMailer.create_signup("jojo@yahoo.com", "Jojo Binks")
end
subject { @email }
it "should be delivered to the email passed in" do
should deliver_to("jojo@yahoo.com")
end
it "should contain the user's name in the mail body" do
@email.should have_body_text(/Jojo Binks/)
end
it "should contain a link to the confirmation page" do
@email.should have_body_text(/#{confirm_account_url(:host => 'example.com')}/)
end
it { should have_subject(/Account confirmation/) }
end
# In this example group more of the documentation is placed in the context trying to allow for more concise specs.
describe "Signup Email" do
include EmailSpec::Helpers
include EmailSpec::Matchers
include ActionController::UrlWriter
before(:all) do
@email = UserMailer.create_signup("jojo@yahoo.com", "Jojo Binks")
end
subject { @email }
it { should have_body_text(/#{confirm_account_url(:host => 'example.com')}/) }
it { should have_subject(/Account confirmation/) }
describe "sent with email address of 'jojo@yahoo.com', and users name 'Jojo Binks'" do
subject { @email }
it { should deliver_to("jojo@yahoo.com") }
it { should have_body_text(/Jojo Binks/) }
end
end
Version data entries
22 entries across 22 versions & 6 rubygems