named_seeds 1.0.4 → 1.0.5

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: faba2937d0e01b1c4fe753d384443646f6a646fa
+  data.tar.gz: 834e8f40a54ddfd993cd06fa185e19bc0aad1dd4
+SHA512:
+  metadata.gz: 05516f577aff9af4ea8fa809410bdd0274096632b9e7a4270acffec2083163fb6789b5abf897b39b3f3968102d96d460a139344c4d4b4331801e547f5cd8b4e8
+  data.tar.gz: 4053bcc81a480683425c944c71c391a7a005e59f62b717949e28b631df468e84333435fcc748bdccf7ad22a6cfbe58c5cd5862303ebf81e9ec9096f00975dff2

data/Gemfile

@@ -1,2 +1,2 @@
-source :rubygems
+source 'https://rubygems.org'
 gemspec

data/README.md

@@ -1,10 +1,10 @@
 # NamedSeeds
 
-**Make you tests fast by augmenting them with transactional fixtures powered by your favorite factory library!**
+**Make your tests fast by augmenting them with transactional fixtures powered by your favorite factory library!**
 
-We all know that ActiveRecord::Fixtures suck because they are authored in YAML files. But Rails did get something right, transactional tests and easy helper methods to access fixtures by name. NamedSeeds aims to be a drop in replacement for Rails fixtures or an enhancement to RSpec and Cucumber while using any object generator of your choice!
+We all know that ActiveRecord::Fixtures are hard to maintain and are disconnected from the models that save your data. But Rails did get something right with transactional tests and easy helper methods to access fixtures by name. NamedSeeds aims to be a drop-in replacement for Rails fixtures or an enhancement to RSpec and Cucumber while using any object generator of your choice!
 
-The idea is to leverage your tests' existing factories to generate fixtures that will be populated before testing starts and to use a database transaction strategy around each test. In this way you have a populated story that can be accessed via convienient helper methods like `users(:admin)` which inturn yields much faster test runs. Database fixtures, even those seeded by factories, are not a pancea and we highly suggested that you continue to use factories in your tests when it makes sense to do so. For those that think this is mad or have FUD to share, please see my blog articles..
+The idea is to leverage your tests' existing factories to generate fixtures that will be populated before testing starts and to use a database transaction strategy around each test. In this way you have a populated story that can be accessed via convienient helper methods like `users(:admin)` which in turn yields much faster test runs. Database fixtures, even those seeded by factories, are not a panacea and we highly suggested that you continue to use factories in your tests when it makes sense to do so. For those that think this is mad or have FUD to share, please see my blog articles:
 
 * Inprogress...
 * Inprogress...
@@ -26,7 +26,7 @@ NamedSeeds requires that you create a `db/test/seeds.rb` file. The contents of t
 
 ```ruby
 require 'factory_girl'
-FactoryGirl.find_definitions rescue true
+FactoryGirl.reload
 
 @bob = FactoryGirl.create :user, :id => NamedSeeds.identify(:bob), :email => 'bob@test.com'
 ```
@@ -38,16 +38,16 @@ Use the `NamedSeeds.identify` method to give a name to the identity used for thi
 
 **Using these tasks manually should not be needed as both are hooked into the proper `test:prepare` and `db:setup` process for you.**
 
-NamedSeeds includes two rake tasks. The `db:test:seeds` is the one that does all the work and is automatically called after Rails' `test:prepare` for you. So running your rake test tasks will create your test database and seed it for you automatically before your tests run.
+NamedSeeds includes two rake tasks. The `db:test:seeds` is the one that does all the work and is automatically called after Rails' `test:prepare` for you. So running your rake test tasks will create your test database and seed it for you automatically before your tests run. Remember, ActiveRecords `db:test:prepare` is not a proper hook, read [my comment](https://github.com/rspec/rspec-rails/issues/663#issuecomment-11831559) on this rspec issue for more details.
 
-The other task is `db:development:seed`. This task invokes the normal Rails' `db:seed` task, then loads the db/test/seeds.rb file while still in development mode. We automatically call this task after `db:setup` for you. This task provides a way for a developer to populate their development database with the same fixture story used for testing. This makes it easy for developers to learn your application as the test story is a 1 to 1 mapping of data in local development.
+The other task is `db:development:seed`. This task invokes the normal Rails `db:seed` task, then loads the db/test/seeds.rb file while still in development mode. We automatically call this task after `db:setup` for you. This task provides a way for a developer to populate their development database with the same fixture story used for testing. This makes it easy for developers to learn your application as the test story is a 1 to 1 mapping of data in local development.
 
 ```shell
 $ rake db:test:seed          # Run the seed data from db/test/seeds.rb and 
-                             # optional your Rails db/seeds.rb if you have 
+                             # optionally your Rails db/seeds.rb if you have 
                              # configured `app_load_seed` below.
 
-$ rake db:development:seed   # Runs the normal Rails `db:seed` task then the 
+$ rake db:development:seed   # Runs the normal Rails `db:seed` task then 
                              # loads the db/test/seeds.rb file.
 ```
 
@@ -95,7 +95,8 @@ Review how helper methods may map to custom table names. Like Rails did with #fi
 
 ## Configurations
 
-NamedSeeds is a `Rails::Railtie` that exposes a few `config` options. So open up the `config/environments/development.rb` **(yes in development.rb)** and use the `config.named_seeds` options below.
+NamedSeeds is a `Rails::Railtie` that exposes a few `config` options. So open up the `config/environments/development.rb` **(yes in development.rb)** and use the `config.named_seeds` options below. NOTE: I have found that sometimes I need to add some configurations to `config/environments/test.rb` too. Mainly when using [spring](https://github.com/jonleighton/spring). So adding `config.named_seeds.app_load_seed = true` is what I needed.
+
 
 * *app_load_seed* - Load your Rails application's db/seeds.rb file into the test database. This is done before db/test/seeds.rb is loaded. Default is false.
 * *engines_with_load_seed* - Some Rails engines provide a load seed hook. If you want NamedSeed to call the engine's seed method into your tests database, push the engine constant to this array. Any object responding to `load_seed` sould work here too. Default is an empty array.
@@ -135,7 +136,7 @@ Show examples with these 3 factory libraries.
 * https://github.com/paulelliott/fabrication
 * https://github.com/notahat/machinist
 
-Setup a dummy_application in test.
+Set up a dummy_application in test.
 
 How are we different from:
 

data/lib/named_seeds/version.rb

@@ -1,3 +1,3 @@
 module NamedSeeds
-  VERSION = "1.0.4"
+  VERSION = "1.0.5"
 end

data/named_seeds.gemspec

@@ -14,9 +14,9 @@ Gem::Specification.new do |gem|
   gem.files         = `git ls-files`.split("\n")
   gem.test_files    = `git ls-files -- {test,spec,features}/*`.split("\n")
   gem.require_paths = ["lib"]
-  gem.add_runtime_dependency     'rails',             '>= 3.1'
+  gem.add_runtime_dependency     'rails', '>= 3.1', '< 4.2'
   gem.add_runtime_dependency     'database_cleaner'
-  gem.add_development_dependency 'sqlite3',           '~> 1.3'
-  gem.add_development_dependency 'rake',              '~> 0.9.2'
-  gem.add_development_dependency 'minitest',          '~> 2.8.1'
+  gem.add_development_dependency 'sqlite3'
+  gem.add_development_dependency 'rake'
+  gem.add_development_dependency 'minitest'
 end

data/test/support/schema.rb

@@ -1,6 +1,6 @@
 ActiveRecord::Base.class_eval do
-  silence do
-    
+  silence(:stdout) do
+
     connection.create_table :users, :force => true do |t|
       t.string :name, :email
     end

metadata

@@ -1,96 +1,91 @@
 --- !ruby/object:Gem::Specification
 name: named_seeds
 version: !ruby/object:Gem::Version
-  version: 1.0.4
-  prerelease: 
+  version: 1.0.5
 platform: ruby
 authors:
 - Ken Collins
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-12-05 00:00:00.000000000 Z
+date: 2014-10-03 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '3.1'
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: '4.2'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '3.1'
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: '4.2'
 - !ruby/object:Gem::Dependency
   name: database_cleaner
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: sqlite3
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ~>
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '1.3'
+        version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ~>
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '1.3'
+        version: '0'
 - !ruby/object:Gem::Dependency
   name: rake
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ~>
+    - - ">="
       - !ruby/object:Gem::Version
-        version: 0.9.2
+        version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ~>
+    - - ">="
       - !ruby/object:Gem::Version
-        version: 0.9.2
+        version: '0'
 - !ruby/object:Gem::Dependency
   name: minitest
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ~>
+    - - ">="
       - !ruby/object:Gem::Version
-        version: 2.8.1
+        version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ~>
+    - - ">="
       - !ruby/object:Gem::Version
-        version: 2.8.1
+        version: '0'
 description: Make you tests fast by augmenting them with transactional fixtures powered
   by your favorite factory library!
 email:
@@ -99,7 +94,7 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- .gitignore
+- ".gitignore"
 - CHANGELOG.md
 - Gemfile
 - LICENSE
@@ -119,31 +114,29 @@ files:
 - test/test_helper.rb
 homepage: http://github.com/metaskills/named_seeds
 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: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.24
+rubygems_version: 2.3.0
 signing_key: 
-specification_version: 3
-summary: ! 'Replace ActiveRecord::Fixtures With #{your_factory_lib}.'
+specification_version: 4
+summary: 'Replace ActiveRecord::Fixtures With #{your_factory_lib}.'
 test_files:
 - test/cases/base_test.rb
 - test/support/models.rb
 - test/support/schema.rb
 - test/test_helper.rb
-has_rdoc: