active_mailer 0.0.9 → 0.0.10

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 99e1d029544140a5c0694c8cdec3e7b64caef636
+  data.tar.gz: 58aa481703fe2dd3ac5a33c7771ac394f1e58a37
+SHA512:
+  metadata.gz: 614db7b69f763e6b4a04bad6d670bdd6fb0830a24c728b6cd2a55b2c1869cbfc75b21e8be1c07c04a2796794e4f1e252e32b0ce4cadc1b19d7ce0d4071db9ac8
+  data.tar.gz: ec33f72e5d074745554c8843cd129b3e70da5c05741fa60ce6dfb3d6d726525c490c0864bc1dbb6bd9eb8822e98483eef62e3822c869e90b4b6bea15e81b863e

data/.gitignore

@@ -5,35 +5,10 @@
 .\#*
 .bundle
 .DS_Store
-.svn
 insight.sqlite
-app/assets/stylesheets/.sass-cache/*
-config/*.sphinx.conf
-coverage
-db/*.bkp
-db/deep_test*
-db/*.sqlite3
-db/*sphinx
-log/test
 log/*.log
-log/*.pid
-log/culerity_page_errors
-public/system
-public/p/*
-public/culerity_page_errors
-public/javascripts/all.js
-public/stylesheets/all.css
-public/images/upload
-public/data
 vendor/bundle
 test/log
 tmp
-coverage.data
-rerun.txt
-test/fixtures/vcr_cassettes
-features/cassettes
-coverage
-bin
-repos
-test/fixtures/repos
-*.gem
+Gemfile.lock
+pkg/

data/{ChangeLog.md → CHANGELOG.md}

@@ -1,15 +1,18 @@
-= 0.0.9
+### 0.0.10
+* Update project to modern Ruby standards.
+
+### 0.0.9
 * okay, this time we are totally setting the headers correctly
 
-= 0.0.8
+### 0.0.8
 * do not coerce headers
 
-= 0.0.7
+### 0.0.7
 * support for setting custom email headers. Give us the hassssh.
 
-= 0.0.6
+### 0.0.6
 * support for setting layouts
 
-= 0.0.5
+### 0.0.5
 * Fixed bug where the subject was not being set correctly.
 * The ActionMailer object used behind the scenese is now available through #mailer

data/Gemfile

@@ -1,15 +1,3 @@
-source "http://rubygems.org"
+source "https://rubygems.org"
 
 gemspec
-
-gem "rails", "=3.2.1"
-gem "capybara", ">= 0.4.0"
-gem "sqlite3"
-
-gem "pry"
-gem "pry-rails"
-gem "pry-nav"
-gem "pry-stack_explorer"  
-
-gem "wrong"
-gem "factory_girl"

data/README.md

@@ -0,0 +1,77 @@
+# ActiveMailer
+
+Email needs to have somewhere to put the business logic surrounding it, and
+the controller is not the place for that.
+
+See the disagreement:
+* http://www.robbyonrails.com/articles/2009/11/16/sending-email-controllers-versus-models
+* http://twitter.com/dhh/status/5769040367
+* http://twitter.com/dhh/status/5769698185
+* http://www.loudthinking.com/posts/43-think-of-emails-as-views-delivered-through-smtp
+
+
+## Installation
+
+1. Add `gem "active_mailer"` to your `Gemfile` and run `bundle install`
+
+2. Run `rails generate active_mailer:install`
+
+3. Run `rake db:migrate`
+
+
+## Basic Usage
+
+There's only a partial generator. In the mean time, making a new ActiveMailer class can be done like this.
+
+1. Run `rails generate model --no-migration --parent ActiveMailer::Base FooEmail`, you can pass any additional columns just like you would for a normal `generate model`.
+
+2. Run `rails generate active_model:migration FooEmail`
+
+3. Make the template for your email (in this case called `foo_email.rb`) in `app/views/active_mailer/base/default_action_mailer`
+
+You're ready! You can send your email by making an instance of `FooEmail`, setting the appropriate details, and calling `send!`.
+
+```ruby
+> f = FooEmail.new(:subject => "My Awesome Email", :sender => "noreply@example.com",
+>                  :recipients => "test@example.com")
+=> #<FooEmail id: nil, blahblahblah>
+
+> f.send!
+=> true
+```
+
+## Advanced Usage
+
+If your email is always going to have the same subject, sender, bcc, etc, then
+you can set those in the ActiveMailer object. Remember that it's really just
+an ActiveRecord object, so you can do anything in this class you can do in
+ActiveRecord.
+
+Here's an example of using ActiveRecord associations to make sure there's a
+user for the email. It also includes setting the subject and sender by
+default.
+
+```ruby
+class BeerEmail < ActiveMailer::Base
+  belongs_to :user
+
+  validates_presence_of :user
+
+  def after_initialize
+    self.subject = "It's Beer O'Clock"
+    self.sender  = "itstime@beeroclock.com"
+  end
+end
+```
+
+## Contributing
+
+[Bugs/Feature](http://www.pivotaltracker.com/projects/14211)
+
+
+## Authors
+
+Matt Gordon
+
+
+Copyright (c) 2009-2015 [Expected Behavior, LLC], released under the MIT license

data/Rakefile

@@ -1,15 +1,8 @@
-# encoding: UTF-8
-require 'rubygems'
-begin
-  require 'bundler/setup'
-rescue LoadError
-  puts 'You must `gem install bundler` and `bundle install` to run rake tasks'
-end
-
+require 'bundler/setup'
 require 'rake'
 require 'rdoc/task'
-
 require 'rake/testtask'
+require 'bundler/gem_tasks'
 
 Rake::TestTask.new(:test) do |t|
   t.libs << 'lib'

data/active_mailer.gemspec

@@ -1,22 +1,29 @@
+$:.push File.expand_path("../lib", __FILE__)
+require "active_mailer/version"
+
 # Provide a simple gemspec so you can easily use your enginex
 # project in your rails apps through git.
 Gem::Specification.new do |s|
   s.name = "active_mailer"
   s.summary     = "Adds model-level validation to emails."
-  s.description = "Application that have complext email sending logic have DRYness problems. ActiveMailersolves that by making a legitimate email model where all sending logic belongs. Also capable of acting as an audit trail for email sending."
+  s.description = "Applications that have complex email sending logic have DRYness problems. ActiveMailer solves that by making a legitimate email model where all sending logic belongs. It is also capable of acting as an audit trail for email sending."
   s.authors     = ["Matt Gordon"]
   s.email       = 'support@expectedbehavior.com'
   s.files = Dir["{app,lib,config}/**/*"] + ["MIT-LICENSE", "Rakefile", "Gemfile", "README.rdoc"]
-  s.version = "0.0.9"
+  s.version = ActiveMailer::VERSION
   s.homepage    =
     'https://github.com/expectedbehavior/active_mailer'
 
 
   s.required_rubygems_version = "> 1.3.6"
 
-  s.add_dependency "activesupport" , "~> 3.2"
   s.add_dependency "rails"         , "~> 3.2"
 
+  s.add_development_dependency(%q<rake>, [">= 0"])
+  s.add_development_dependency(%q<wrong>, ["~> 0.7.0"])
+  s.add_development_dependency(%q<sqlite3>, [">= 1.3.5"])
+  s.add_development_dependency(%q<test-unit>, ["~> 3.0.0"])
+
   s.files = `git ls-files`.split("\n")
   s.executables = `git ls-files`.split("\n").map{|f| f =~ /^bin\/(.*)/ ? $1 : nil}.compact
   s.require_path = 'lib'

data/app/models/active_mailer/base.rb

@@ -1,8 +1,3 @@
-# require 'email_user'
-# require 'email_user_association'
-# require 'action_controller'
-# require 'application_helper'
-# require 'action_controller/url_writer'
 module ActiveMailer #:nodoc:
   class Base < ActiveRecord::Base
     self.abstract_class = true
@@ -167,7 +162,6 @@ module ActiveMailer #:nodoc:
             attachments_to_set = (options[:attachments] || [])
             options.keys.each do |k|
               self.instance_eval("@#{k.to_s} = options[k]") if options[k]
-#              instance_variable_set(k.to_s, options[k])
             end
 
             attachments_to_set.each do |att|
@@ -189,7 +183,7 @@ module ActiveMailer #:nodoc:
       end
 
       def default_email_method_name
-        "#{self.name.underscore}"
+        name.underscore
       end
     end
   end

data/lib/active_mailer/version.rb

@@ -0,0 +1,3 @@
+module ActiveMailer
+  VERSION = "0.0.10"
+end

data/lib/generators/active_mailer/migration/templates/migration.rb

@@ -1,13 +1,13 @@
 class <%= migration_class_name %> < ActiveRecord::Migration
   def change
-    create_table :<%= table_name %> do |t|
+    create_active_mailer_table :<%= table_name %> do |t|
 <% attributes.each do |attribute| -%>
       t.<%= attribute.type %> :<%= attribute.name %><%= attribute.inject_options %>
 <% end -%>
 
       t.integer   :sender_id
       t.timestamp :sent_at
-      t.string    :subject      
+      t.string    :subject
 
       t.timestamps
     end

data/test/active_mailer_test.rb

@@ -25,7 +25,10 @@ class ActiveMailerTest < ActiveSupport::TestCase
 
   test "sends with correct layout" do
     InvitationEmail.layout "email"
-    email = create(:invitation_email)
+    email = InvitationEmail.new(:sender => "spammy@example.com",
+                                :recipients => ["takesit@upemail.com", nil],
+                                :subject => "YOU GUYS!"
+                                )
     assert { email.send! }
     actual_layout = ActiveMailer::Base::DefaultActionMailer.instance_variable_get("@_layout")
     assert { "email" == actual_layout  }

data/test/fixtures/dummyapp_rails_3.2/Gemfile.lock

@@ -1,8 +1,7 @@
 PATH
-  remote: /Users/esquivalient/code/active_mailer
+  remote: ../../..
   specs:
-    active_mailer (0.0.5)
-      activesupport (~> 3.2)
+    active_mailer (0.0.9)
       rails (~> 3.2)
 
 GEM

data/test/test_helper.rb

@@ -4,9 +4,7 @@ ENV["RAILS_ENV"] = "test"
 require File.expand_path("../fixtures/dummyapp_rails_3.2/config/environment.rb",  __FILE__)
 require "rails/test_help"
 
-require "factory_girl"
-include FactoryGirl::Syntax::Methods
-FactoryGirl.find_definitions
+require "wrong"
 
 # ActionMailer::Base.delivery_method = :test
 # ActionMailer::Base.perform_deliveries = true
@@ -14,11 +12,6 @@ FactoryGirl.find_definitions
 
 # Rails.backtrace_cleaner.remove_silencers!
 
-# Configure capybara for integration testing
-# require "capybara/rails"
-# Capybara.default_driver   = :rack_test
-# Capybara.default_selector = :css
-
 # Run any available migration
 ActiveRecord::Migrator.migrate File.expand_path("../fixtures/dummyapp_rails_3.2/db/migrate/", __FILE__)
 

metadata

@@ -1,62 +1,98 @@
 --- !ruby/object:Gem::Specification
 name: active_mailer
 version: !ruby/object:Gem::Version
-  version: 0.0.9
-  prerelease: 
+  version: 0.0.10
 platform: ruby
 authors:
 - Matt Gordon
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-06-17 00:00:00.000000000 Z
+date: 2015-06-25 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
-  name: activesupport
+  name: rails
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ~>
+    - - "~>"
       - !ruby/object:Gem::Version
         version: '3.2'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ~>
+    - - "~>"
       - !ruby/object:Gem::Version
         version: '3.2'
 - !ruby/object:Gem::Dependency
-  name: rails
+  name: rake
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ~>
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '3.2'
-  type: :runtime
+        version: '0'
+  type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ~>
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '3.2'
-description: Application that have complext email sending logic have DRYness problems.
-  ActiveMailersolves that by making a legitimate email model where all sending logic
-  belongs. Also capable of acting as an audit trail for email sending.
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: wrong
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.7.0
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.7.0
+- !ruby/object:Gem::Dependency
+  name: sqlite3
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.3.5
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.3.5
+- !ruby/object:Gem::Dependency
+  name: test-unit
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 3.0.0
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 3.0.0
+description: Applications that have complex email sending logic have DRYness problems.
+  ActiveMailer solves that by making a legitimate email model where all sending logic
+  belongs. It is also capable of acting as an audit trail for email sending.
 email: support@expectedbehavior.com
 executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- .gitignore
-- ChangeLog.md
+- ".gitignore"
+- CHANGELOG.md
 - Gemfile
-- Gemfile.lock
 - MIT-LICENSE
-- README
+- README.md
 - Rakefile
 - active_mailer.gemspec
 - app/models/active_mailer/base.rb
@@ -64,6 +100,7 @@ files:
 - app/models/active_mailer/email_user_association.rb
 - lib/active_mailer.rb
 - lib/active_mailer/engine.rb
+- lib/active_mailer/version.rb
 - lib/generators/active_mailer/install/install_generator.rb
 - lib/generators/active_mailer/install/templates/migration.rb
 - lib/generators/active_mailer/migration/migration_generator.rb
@@ -4484,30 +4521,28 @@ files:
 - test/fixtures/dummyapp_rails_3.2/vendor/bundle/ruby/1.9.1/specifications/tzinfo-0.3.35.gemspec
 - test/fixtures/dummyapp_rails_3.2/vendor/bundle/ruby/1.9.1/specifications/uglifier-1.3.0.gemspec
 - test/fixtures/dummyapp_rails_3.2/vendor/plugins/.gitkeep
-- test/support/integration_case.rb
 - test/test_helper.rb
 homepage: https://github.com/expectedbehavior/active_mailer
 licenses: []
+metadata: {}
 post_install_message: 
 rdoc_options: []
 require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
-  none: false
   requirements:
-  - - ! '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
-  none: false
   requirements:
-  - - ! '>'
+  - - ">"
     - !ruby/object:Gem::Version
       version: 1.3.6
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.23
+rubygems_version: 2.4.8
 signing_key: 
-specification_version: 3
+specification_version: 4
 summary: Adds model-level validation to emails.
 test_files: []

data/Gemfile.lock

@@ -1,154 +0,0 @@
-PATH
-  remote: .
-  specs:
-    active_mailer (0.0.9)
-      activesupport (~> 3.2)
-      rails (~> 3.2)
-
-GEM
-  remote: http://rubygems.org/
-  specs:
-    actionmailer (3.2.1)
-      actionpack (= 3.2.1)
-      mail (~> 2.4.0)
-    actionpack (3.2.1)
-      activemodel (= 3.2.1)
-      activesupport (= 3.2.1)
-      builder (~> 3.0.0)
-      erubis (~> 2.7.0)
-      journey (~> 1.0.1)
-      rack (~> 1.4.0)
-      rack-cache (~> 1.1)
-      rack-test (~> 0.6.1)
-      sprockets (~> 2.1.2)
-    activemodel (3.2.1)
-      activesupport (= 3.2.1)
-      builder (~> 3.0.0)
-    activerecord (3.2.1)
-      activemodel (= 3.2.1)
-      activesupport (= 3.2.1)
-      arel (~> 3.0.0)
-      tzinfo (~> 0.3.29)
-    activeresource (3.2.1)
-      activemodel (= 3.2.1)
-      activesupport (= 3.2.1)
-    activesupport (3.2.1)
-      i18n (~> 0.6)
-      multi_json (~> 1.0)
-    arel (3.0.0)
-    binding_of_caller (0.7.1)
-      debug_inspector (>= 0.0.1)
-    builder (3.0.0)
-    capybara (1.1.2)
-      mime-types (>= 1.16)
-      nokogiri (>= 1.3.3)
-      rack (>= 1.0.0)
-      rack-test (>= 0.5.4)
-      selenium-webdriver (~> 2.0)
-      xpath (~> 0.1.4)
-    childprocess (0.3.1)
-      ffi (~> 1.0.6)
-    coderay (1.0.8)
-    debug_inspector (0.0.2)
-    diff-lcs (1.1.3)
-    erubis (2.7.0)
-    factory_girl (4.2.0)
-      activesupport (>= 3.0.0)
-    ffi (1.0.11)
-    hike (1.2.1)
-    i18n (0.6.0)
-    journey (1.0.1)
-    json (1.6.5)
-    mail (2.4.1)
-      i18n (>= 0.4.0)
-      mime-types (~> 1.16)
-      treetop (~> 1.4.8)
-    method_source (0.8.1)
-    mime-types (1.17.2)
-    multi_json (1.0.4)
-    nokogiri (1.5.0)
-    polyglot (0.3.3)
-    predicated (0.2.6)
-    pry (0.9.12)
-      coderay (~> 1.0.5)
-      method_source (~> 0.8)
-      slop (~> 3.4)
-    pry-nav (0.2.3)
-      pry (~> 0.9.10)
-    pry-rails (0.2.2)
-      pry (>= 0.9.10)
-    pry-stack_explorer (0.4.9)
-      binding_of_caller (>= 0.7)
-      pry (~> 0.9.11)
-    rack (1.4.1)
-    rack-cache (1.1)
-      rack (>= 0.4)
-    rack-ssl (1.3.2)
-      rack
-    rack-test (0.6.1)
-      rack (>= 1.0)
-    rails (3.2.1)
-      actionmailer (= 3.2.1)
-      actionpack (= 3.2.1)
-      activerecord (= 3.2.1)
-      activeresource (= 3.2.1)
-      activesupport (= 3.2.1)
-      bundler (~> 1.0)
-      railties (= 3.2.1)
-    railties (3.2.1)
-      actionpack (= 3.2.1)
-      activesupport (= 3.2.1)
-      rack-ssl (~> 1.3.2)
-      rake (>= 0.8.7)
-      rdoc (~> 3.4)
-      thor (~> 0.14.6)
-    rake (0.9.2.2)
-    rdoc (3.12)
-      json (~> 1.4)
-    ruby2ruby (2.0.3)
-      ruby_parser (~> 3.1)
-      sexp_processor (~> 4.0)
-    ruby_parser (3.1.1)
-      sexp_processor (~> 4.1)
-    rubyzip (0.9.6.1)
-    selenium-webdriver (2.19.0)
-      childprocess (>= 0.2.5)
-      ffi (~> 1.0.9)
-      multi_json (~> 1.0.4)
-      rubyzip
-    sexp_processor (4.1.5)
-    slop (3.4.3)
-    sprockets (2.1.2)
-      hike (~> 1.2)
-      rack (~> 1.0)
-      tilt (~> 1.1, != 1.3.0)
-    sqlite3 (1.3.5)
-    thor (0.14.6)
-    tilt (1.3.3)
-    treetop (1.4.10)
-      polyglot
-      polyglot (>= 0.3.1)
-    tzinfo (0.3.31)
-    wrong (0.7.0)
-      diff-lcs (~> 1.1.2)
-      predicated (~> 0.2.6)
-      ruby2ruby (>= 2.0.1)
-      ruby_parser (>= 3.0.1)
-      sexp_processor (>= 4.0)
-    xpath (0.1.4)
-      nokogiri (~> 1.3)
-
-PLATFORMS
-  ruby
-
-DEPENDENCIES
-  active_mailer!
-  capybara (>= 0.4.0)
-  factory_girl
-  pry
-  pry-nav
-  pry-rails
-  pry-stack_explorer
-  rails (= 3.2.1)
-  sqlite3
-  wrong

data/README

@@ -1,111 +0,0 @@
-ActiveMailer
-============
-
-Introduction goes here.
-
-DHH thinks this is a bad idea and he's wrong. Email needs to have somewhere to put the business
-logic surrounding it, and the controller is not the place for that.
-http://www.robbyonrails.com/articles/2009/11/16/sending-email-controllers-versus-models
-http://twitter.com/dhh/status/5769040367
-http://twitter.com/dhh/status/5769698185
-http://www.loudthinking.com/posts/43-think-of-emails-as-views-delivered-through-smtp
-
-
-Installation
-============
-
-1) script/plugin install git://github.com/expectedbehavior/active_mailer.git
-
-2) Make the tables for the classes that ActiveMailer uses to store the people you send email to. There's no need to make the models; those are included with the plugin.
-
-class CreateActiveMailerTables < ActiveRecord::Migration
-  def self.up
-    create_table :email_users do |t|
-      t.string :email_address
-      t.timestamps
-    end
-    
-    create_table :email_user_associations do |t|
-      t.references :email_user
-      t.string :emailable_type
-      t.integer :emailable_id
-      t.timestamps
-    end
-  end
-
-  def self.down
-    drop_table :email_users
-    drop_table :email_user_associations
-  end
-end
-
-
-Basic Usage
-===========
-
-There's no generator yet (high on the list of things to do). In the mean time, making a new ActiveMailer class can be done like this.
-
-1) script/generate model FooEmail # or whatever you want to call your email
-
-2) Open up the FooEmail model and change "ActiveRecord::Base" to "ActiveMailer::Base"
-
-3) Open up the FooEmail migration and use "create_active_mailer_table" instead of the usual "create_table".
-
-# sample active mailer migration
-class CreateFooEmail < ActiveRecord::Migration
-  def self.up
-    create_active_mailer_table :foo_emails do |t|
-      t.integer :registration_id
-      t.string  :kind
-      t.timestamps
-    end
-  end
-
-  def self.down
-    drop_table :foo_emails
-  end
-end
-
-4) Make the template for your email (in this case called 'foo_email.rb') in app/views/active_mailer/base/default_action_mailer
-
-At this point, there's no need to do any more. You can send your email by making an object, setting the appropriate details, and calling send.
-
-> f = FooEmail.new(:subject => "My Awesome Email", :sender => "noreply@example.com", :recipients => "test@example.com")
-=> #<FooEmail id: nil, blahblahblah>
-
-> f.send!
-=> true
-
-
-More Advanced Usage
-===================
-
-If your email is always going to have the same subject, sender, bcc, etc, then you can always set those things in the mail object. Remember that it's really just an ActiveRecord object, so you can do anything in this class you can do in ActiveRecord. Here's an example of using ActiveRecord associations to make sure there's a user for the email. It also includes setting the subject and sender by default.
-
-class BeerEmail < ActiveMailer::Base
-  belongs_to :user
-
-  validates_presence_of :user
-  
-  def after_initialize
-    self.subject = "It's Beer O'Clock"
-    self.sender  = "itstime@beeroclock.com"
-  end
-end
-
-
-
-Contributing
-============
-
-Bugs/Feature
-http://www.pivotaltracker.com/projects/14211
-
-Authors
-=======
-Matt Gordon
-
-
-Copyright (c) 2009 [Expected Behavior, LLC], released under the MIT license
-
-

data/test/support/integration_case.rb

@@ -1,5 +0,0 @@
-# Define a bare test case to use with Capybara
-class ActiveSupport::IntegrationCase < ActiveSupport::TestCase
-  include Capybara::DSL
-  include Rails.application.routes.url_helpers
-end