email_spec 1.2.1 → 1.4.0

data/examples/rails3_root/config/application.rb

@@ -1,43 +0,0 @@
-require File.expand_path('../boot', __FILE__)
-
-require 'rails/all'
-
-# If you have a Gemfile, require the gems listed there, including any gems
-# you've limited to :test, :development, or :production.
-Bundler.require(:default, Rails.env) if defined?(Bundler)
-
-module Rails3Root
-  class Application < Rails::Application
-    # Settings in config/environments/* take precedence over those specified here.
-    # Application configuration should go into files in config/initializers
-    # -- all .rb files in that directory are automatically loaded.
-
-    # Add additional load paths for your own custom dirs
-    # config.load_paths += %W( #{config.root}/extras )
-
-    # Only load the plugins named here, in the order given (default is alphabetical).
-    # :all can be used as a placeholder for all plugins not explicitly named
-    # config.plugins = [ :exception_notification, :ssl_requirement, :all ]
-
-    # Activate observers that should always be running
-    # config.active_record.observers = :cacher, :garbage_collector, :forum_observer
-
-    # Set Time.zone default to the specified zone and make Active Record auto-convert to this zone.
-    # Run "rake -D time" for a list of tasks for finding time zone names. Default is UTC.
-    # config.time_zone = 'Central Time (US & Canada)'
-
-    # The default locale is :en and all translations from config/locales/*.rb,yml are auto loaded.
-    # config.i18n.load_path += Dir[Rails.root.join('my', 'locales', '*.{rb,yml}').to_s]
-    # config.i18n.default_locale = :de
-
-    # Configure generators values. Many other options are available, be sure to check the documentation.
-    # config.generators do |g|
-    #   g.orm             :active_record
-    #   g.template_engine :erb
-    #   g.test_framework  :test_unit, :fixture => true
-    # end
-
-    # Configure sensitive parameters which will be filtered from the log file.
-    config.filter_parameters << :password
-  end
-end

data/examples/rails3_root/config/boot.rb

@@ -1,14 +0,0 @@
-# Use locked gems if present.
-begin
-  require File.expand_path('../../.bundle/environment', __FILE__)
-
-rescue LoadError
-  # Otherwise, use RubyGems.
-  require 'rubygems'
-
-  # And set up the gems listed in the Gemfile.
-  if File.exist?(File.expand_path('../../Gemfile', __FILE__))
-    require 'bundler'
-    Bundler.setup
-  end
-end

data/examples/rails3_root/config/cucumber.yml

@@ -1,8 +0,0 @@
-<%
-rerun = File.file?('rerun.txt') ? IO.read('rerun.txt') : ""
-rerun_opts = rerun.to_s.strip.empty? ? "--format #{ENV['CUCUMBER_FORMAT'] || 'progress'} features" : "--format #{ENV['CUCUMBER_FORMAT'] || 'pretty'} #{rerun}"
-std_opts = "--format #{ENV['CUCUMBER_FORMAT'] || 'progress'} --strict --tags ~@wip"
-%>
-default: <%= std_opts %> features
-wip: --tags @wip:3 --wip features
-rerun: <%= rerun_opts %> --format rerun --out rerun.txt --strict --tags ~@wip

data/examples/rails3_root/config/database.yml

@@ -1,25 +0,0 @@
-# SQLite version 3.x
-#   gem install sqlite3-ruby (not necessary on OS X Leopard)
-development:
-  adapter: sqlite3
-  database: db/development.sqlite3
-  pool: 5
-  timeout: 5000
-
-# Warning: The database defined as "test" will be erased and
-# re-generated from your development database when you run "rake".
-# Do not set this db to the same as development or production.
-test: &TEST
-  adapter: sqlite3
-  database: db/test.sqlite3
-  pool: 5
-  timeout: 5000
-
-production:
-  adapter: sqlite3
-  database: db/production.sqlite3
-  pool: 5
-  timeout: 5000
-
-cucumber:
-  <<: *TEST

data/examples/rails3_root/config/environment.rb

@@ -1,6 +0,0 @@
-# Load the rails application
-require File.expand_path('../application', __FILE__)
-
-# Initialize the rails application
-Rails3Root::Application.initialize!
-ActionMailer::Base.default_url_options = { :host => 'example.com' }

data/examples/rails3_root/config/environments/development.rb

@@ -1,20 +0,0 @@
-Rails3Root::Application.configure do
-  # Settings specified here will take precedence over those in config/environment.rb
-
-  # In the development environment your application's code is reloaded on
-  # every request.  This slows down response time but is perfect for development
-  # since you don't have to restart the webserver when you make code changes.
-  config.cache_classes = false
-
-  # Log error messages when you accidentally call methods on nil.
-  config.whiny_nils = true
-
-  # Show full error reports and disable caching
-  config.consider_all_requests_local       = true
-  config.action_view.debug_rjs             = true
-  config.action_controller.perform_caching = false
-
-  # Don't care if the mailer can't send
-  config.action_mailer.raise_delivery_errors = false
-  config.active_support.deprecation = :stderr
-end

data/examples/rails3_root/config/environments/production.rb

@@ -1,42 +0,0 @@
-Rails3Root::Application.configure do
-  # Settings specified here will take precedence over those in config/environment.rb
-
-  # The production environment is meant for finished, "live" apps.
-  # Code is not reloaded between requests
-  config.cache_classes = true
-
-  # Full error reports are disabled and caching is turned on
-  config.consider_all_requests_local       = false
-  config.action_controller.perform_caching = true
-
-  # Specifies the header that your server uses for sending files
-  config.action_dispatch.x_sendfile_header = "X-Sendfile"
-
-  # For nginx:
-  # config.action_dispatch.x_sendfile_header = 'X-Accel-Redirect'
-
-  # If you have no front-end server that supports something like X-Sendfile,
-  # just comment this out and Rails will serve the files
-
-  # See everything in the log (default is :info)
-  # config.log_level = :debug
-
-  # Use a different logger for distributed setups
-  # config.logger = SyslogLogger.new
-
-  # Use a different cache store in production
-  # config.cache_store = :mem_cache_store
-
-  # Disable Rails's static asset server
-  # In production, Apache or nginx will already do this
-  config.serve_static_assets = false
-
-  # Enable serving of images, stylesheets, and javascripts from an asset server
-  # config.action_controller.asset_host = "http://assets.example.com"
-
-  # Disable delivery errors, bad email addresses will be ignored
-  # config.action_mailer.raise_delivery_errors = false
-
-  # Enable threaded mode
-  # config.threadsafe!
-end

data/examples/rails3_root/config/environments/test.rb

@@ -1,30 +0,0 @@
-Rails3Root::Application.configure do
-  # Settings specified here will take precedence over those in config/environment.rb
-
-  # The test environment is used exclusively to run your application's
-  # test suite.  You never need to work with it otherwise.  Remember that
-  # your test database is "scratch space" for the test suite and is wiped
-  # and recreated between test runs.  Don't rely on the data there!
-  config.cache_classes = true
-
-  # Log error messages when you accidentally call methods on nil.
-  config.whiny_nils = true
-
-  # Show full error reports and disable caching
-  config.consider_all_requests_local       = true
-  config.action_controller.perform_caching = false
-
-  # Disable request forgery protection in test environment
-  config.action_controller.allow_forgery_protection    = false
-
-  # Tell Action Mailer not to deliver emails to the real world.
-  # The :test delivery method accumulates sent emails in the
-  # ActionMailer::Base.deliveries array.
-  config.action_mailer.delivery_method = :test
-
-  # Use SQL instead of Active Record's schema dumper when creating the test database.
-  # This is necessary if your schema can't be completely dumped by the schema dumper,
-  # like if you have constraints or database-specific column types
-  # config.active_record.schema_format = :sql
-  config.active_support.deprecation = :stderr
-end

data/examples/rails3_root/config/initializers/backtrace_silencers.rb

@@ -1,7 +0,0 @@
-# Be sure to restart your server when you modify this file.
-
-# You can add backtrace silencers for libraries that you're using but don't wish to see in your backtraces.
-# Rails.backtrace_cleaner.add_silencer { |line| line =~ /my_noisy_library/ }
-
-# You can also remove all the silencers if you're trying to debug a problem that might stem from framework code.
-# Rails.backtrace_cleaner.remove_silencers!

data/examples/rails3_root/config/initializers/cookie_verification_secret.rb

@@ -1,7 +0,0 @@
-# Be sure to restart your server when you modify this file.
-
-# Your secret key for verifying the integrity of signed cookies.
-# If you change this key, all old signed cookies will become invalid!
-# Make sure the secret is at least 30 characters and all random, 
-# no regular words or you'll be exposed to dictionary attacks.
-Rails.application.config.secret_token = 'c63e0079364c42f86ef0256e8eb5e8f6993b30f1e64e4374f5211ddf4efdcd0895282c6383bd58dc817716b7ecc15f52de122e2df27fa326266d4163e4e5fe7d'

data/examples/rails3_root/config/initializers/delayed_job.rb

@@ -1 +0,0 @@
-Delayed::Worker.backend = :active_record

data/examples/rails3_root/config/initializers/inflections.rb

@@ -1,10 +0,0 @@
-# Be sure to restart your server when you modify this file.
-
-# Add new inflection rules using the following format 
-# (all these examples are active by default):
-# ActiveSupport::Inflector.inflections do |inflect|
-#   inflect.plural /^(ox)$/i, '\1en'
-#   inflect.singular /^(ox)en/i, '\1'
-#   inflect.irregular 'person', 'people'
-#   inflect.uncountable %w( fish sheep )
-# end

data/examples/rails3_root/config/initializers/mime_types.rb

@@ -1,5 +0,0 @@
-# Be sure to restart your server when you modify this file.
-
-# Add new mime types for use in respond_to blocks:
-# Mime::Type.register "text/richtext", :rtf
-# Mime::Type.register_alias "text/html", :iphone

data/examples/rails3_root/config/initializers/notifier_job.rb

@@ -1 +0,0 @@
-require 'notifier_job'

data/examples/rails3_root/config/initializers/rspec_generator.rb

@@ -1,6 +0,0 @@
-Rails3Root::Application.configure do
-  config.generators do |g|
-    g.integration_tool :rspec
-    g.test_framework   :rspec
-  end
-end

data/examples/rails3_root/config/initializers/session_store.rb

@@ -1,10 +0,0 @@
-# Be sure to restart your server when you modify this file.
-
-Rails.application.config.session_store :cookie_store, {
-  :key => '_rails3_root_session',
-}
-
-# Use the database for sessions instead of the cookie-based default,
-# which shouldn't be used to store highly confidential information
-# (create the session table with "rake db:sessions:create")
-# Rails.application.config.session_store :active_record_store

data/examples/rails3_root/config/locales/en.yml

@@ -1,5 +0,0 @@
-# Sample localization file for English. Add more files in this directory for other locales.
-# See http://github.com/svenfuchs/rails-i18n/tree/master/rails%2Flocale for starting points.
-
-en:
-  hello: "Hello world"

data/examples/rails3_root/config/routes.rb

@@ -1,7 +0,0 @@
-Rails3Root::Application.routes.draw do
-  root :to => "welcome#index"
-  match "/confirm" => "welcome#confirm", :as => :confirm_account
-  match "/newsletter" => "welcome#newsletter", :as => :request_newsletter
-  match "/attachments" => "welcome#attachments", :as => :request_attachments
-  match "/welcome/signup" => "welcome#signup"
-end

data/examples/rails3_root/db/migrate/20090125013728_create_users.rb

@@ -1,11 +0,0 @@
-class CreateUsers < ActiveRecord::Migration
-  def self.up
-    create_table :users do |t|
-      t.string :email, :name
-    end
-  end
-
-  def self.down
-    drop_table :users
-  end
-end

data/examples/rails3_root/db/migrate/20090908054656_create_delayed_jobs.rb

@@ -1,20 +0,0 @@
-class CreateDelayedJobs < ActiveRecord::Migration
-  def self.up
-    create_table :delayed_jobs, :force => true do |table|
-      table.integer  :priority, :default => 0      # Allows some jobs to jump to the front of the queue
-      table.integer  :attempts, :default => 0      # Provides for retries, but still fail eventually.
-      table.text     :handler                      # YAML-encoded string of the object that will do work
-      table.text     :last_error                   # reason for last failure (See Note below)
-      table.datetime :run_at                       # When to run. Could be Time.now for immediately, or sometime in the future.
-      table.datetime :locked_at                    # Set when a client is working on this object
-      table.datetime :failed_at                    # Set when all retries have failed (actually, by default, the record is deleted instead)
-      table.string   :locked_by                    # Who is working on this object (if locked)
-      table.timestamps
-    end
-
-  end
-  
-  def self.down
-    drop_table :delayed_jobs  
-  end
-end

data/examples/rails3_root/db/schema.rb

@@ -1,33 +0,0 @@
-# This file is auto-generated from the current state of the database. Instead 
-# of editing this file, please use the migrations feature of Active Record to
-# incrementally modify your database, and then regenerate this schema definition.
-#
-# Note that this schema.rb definition is the authoritative source for your 
-# database schema. If you need to create the application database on another
-# system, you should be using db:schema:load, not running all the migrations
-# from scratch. The latter is a flawed and unsustainable approach (the more migrations
-# you'll amass, the slower it'll run and the greater likelihood for issues).
-#
-# It's strongly recommended to check this file into your version control system.
-
-ActiveRecord::Schema.define(:version => 20090908054656) do
-
-  create_table "delayed_jobs", :force => true do |t|
-    t.integer  "priority",   :default => 0
-    t.integer  "attempts",   :default => 0
-    t.text     "handler"
-    t.text     "last_error"
-    t.datetime "run_at"
-    t.datetime "locked_at"
-    t.datetime "failed_at"
-    t.string   "locked_by"
-    t.datetime "created_at"
-    t.datetime "updated_at"
-  end
-
-  create_table "users", :force => true do |t|
-    t.string "email"
-    t.string "name"
-  end
-
-end

data/examples/rails3_root/db/seeds.rb

@@ -1,7 +0,0 @@
-# This file should contain all the record creation needed to seed the database with its default values.
-# The data can then be loaded with the rake db:seed (or created alongside the db with db:setup).
-#
-# Examples:
-#
-#   cities = City.create([{ :name => 'Chicago' }, { :name => 'Copenhagen' }])
-#   Mayor.create(:name => 'Daley', :city => cities.first)

data/examples/rails3_root/doc/README_FOR_APP

@@ -1,2 +0,0 @@
-Use this README file to introduce your application and point to useful places in the API for learning more.
-Run "rake doc:app" to generate API documentation for your models, controllers, helpers, and libraries.

data/examples/rails3_root/features/attachments.feature

@@ -1,27 +0,0 @@
-Feature: Attachment testing support
-  In order for developers to test attachments in emails
-  I want to be able to provide working steps which inspect attachments
-
-  Scenario: Email with Attachments
-    Given no emails have been sent
-    And I go to request attachments be sent to me
-    Then I should receive an email
-    When I open the email
-    Then I should see 2 attachments with the email
-    And there should be an attachment named "image.png"
-    And there should be an attachment named "document.pdf"
-    And attachment 1 should be named "image.png"
-    And attachment 2 should be named "document.pdf"
-    And there should be an attachment of type "image/png"
-    And there should be an attachment of type "application/pdf"
-    And attachment 1 should be of type "image/png"
-    And attachment 2 should be of type "application/pdf"
-    And all attachments should not be blank
-
-  Scenario: Email without Attachments
-    Given no emails have been sent
-    And I am on the homepage
-    And I submit my registration information
-    Then I should receive an email
-    When I open the email
-    Then I should see no attachments with the email

data/examples/rails3_root/features/delayed_job.feature

@@ -1,13 +0,0 @@
-Feature: Delayed Job support
-  In order for developers using delayed_job to test emails
-  I want to be able to provide a compatibility layer, which
-  should run all delayed jobs before checking email boxes
-  In order to populate deliveries done via send_later
-
-  Scenario: Newsletter
-    Given no emails have been sent
-    And I go to request a newsletter
-    Then I should receive an email
-    And I should have 1 email
-    When I open the email
-    Then I should see "Newsletter sent" in the email subject

data/examples/rails3_root/features/errors.feature

@@ -1,40 +0,0 @@
-Feature: Email-spec errors example
-  In order to help alleviate email testing in apps
-  As a email-spec contributor I a newcomer
-  Should be able to easily determine where I have gone wrong
-  These scenarios should fail with helpful messages
-
-  Background:
-    Given I am on the homepage
-    And no emails have been sent
-    When I fill in "Email" with "example@example.com"
-    And I press "Sign up"
-
-  Scenario: I fail to open an email with incorrect subject
-    Then I should receive an email
-    When "example@example.com" opens the email with subject "no email"
-
-  Scenario: I fail to open an email with incorrect subject
-    Then I should receive an email
-    When "example@example.com" opens the email with subject /no email/
-
-  Scenario: I fail to open an email with incorrect text
-    Then I should receive an email
-    When "example@example.com" opens the email with text "no email"
-
-  Scenario: I fail to open an email with incorrect text
-    Then I should receive an email
-    When "example@example.com" opens the email with text /no email/
-
-  Scenario: I fail to receive an email with the expected link
-    Then I should receive an email
-    When I open the email
-    When I follow "link that doesn't exist" in the email
-
-  Scenario: I attempt to operate on an email that is not opened
-    Then I should receive an email
-    When I follow "confirm" in the email
-
-  Scenario: I attempt to check out an unopened email
-    Then I should see "confirm" in the email body
-    And I should see "Account confirmation" in the email subject

data/examples/rails3_root/features/example.feature

@@ -1,93 +0,0 @@
-Feature: EmailSpec Example -- Prevent Bots from creating accounts
-
-  In order to help alleviate email testing in apps
-  As an email-spec contributor I want new users of the library
-  to easily adopt email-spec in their app by following this example
-
-  In order to prevent bots from setting up new accounts
-  As a site manager I want new users
-  to verify their email address with a confirmation link
-
-  Background:
-    Given no emails have been sent
-    And I am a real person wanting to sign up for an account
-    And I am on the homepage
-    And I submit my registration information
-
-  Scenario: First person signup (as myself) with three ways of opening email
-    Then I should receive an email
-    And I should have 1 email
-
-    # Opening email #1
-    When I open the email
-    Then I should see "Account confirmation" in the email subject
-    And I should see "Joe Someone" in the email body
-    And I should see "confirm" in the email body
-
-    # Opening email #2
-    When I open the email with subject "Account confirmation"
-    Then I should see "Account confirmation" in the email subject
-    And I should see "Joe Someone" in the email body
-    And I should see "confirm" in the email body
-
-    # Opening email #3
-    When I open the email with subject /Account confirmation/
-    Then I should see "Account confirmation" in the email subject
-    And I should see "Joe Someone" in the email body
-    And I should see "confirm" in the email body
-
-    When I follow "Click here to confirm your account!" in the email
-    Then I should see "Confirm your new account"
-
-    And "foo@bar.com" should have no emails
-
-  Scenario: Third person signup (emails sent to others) with three ways of opening email
-    Then "foo@bar.com" should have no emails
-    And "example@example.com" should receive an email
-    And "example@example.com" should have 1 email
-
-    # Opening email #1
-    When they open the email
-    Then they should see "Account confirmation" in the email subject
-    And they should see "Joe Someone" in the email body
-    And they should see "confirm" in the email body
-
-    # Opening email #2
-    When "example@example.com" opens the email with subject "Account confirmation"
-    Then they should see "Account confirmation" in the email subject
-    And they should see "Joe Someone" in the email body
-    And they should see "confirm" in the email body
-
-    # Opening email #3
-    When "example@example.com" opens the email with subject /Account confirmation/
-    Then they should see "Account confirmation" in the email subject
-    And they should see "Joe Someone" in the email body
-    And they should see "confirm" in the email body
-
-    When they follow "Click here to confirm your account!" in the email
-    Then they should see "Confirm your new account"
-
-  Scenario: Declarative First Person signup
-    Then I should receive an email with a link to a confirmation page
-
-  Scenario: Declarative First Person signup
-    Then they should receive an email with a link to a confirmation page
-  
-  Scenario: Checking for text in different parts
-    Then I should receive an email
-    And I should have 1 email
-
-    # Opening email #1
-    When I open the email
-    Then I should see "This is the HTML part" in the email html part body
-    And I should see "This is the text part" in the email text part body
-
-    # Opening email #2
-    When I open the email with text "This is the HTML part"
-    Then I should see "This is the HTML part" in the email html part body
-    And I should see "This is the text part" in the email text part body
-
-    # Opening email #3
-    When I open the email with text /This is the HTML part/
-    Then I should see "This is the HTML part" in the email html part body
-    And I should see "This is the text part" in the email text part body