factory_girl 4.7.0 → 4.8.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: fa9eb22350ba005f4e5f9a78f10e5dd825035c21
-  data.tar.gz: 2dcd957723bd03f85b6dbc4a674f031873a29a90
+  metadata.gz: b54b15d2754297ebbbe0bfae279af379d149cb14
+  data.tar.gz: e1704ba19386de1e4f10949b5239e5b8bb7374b7
 SHA512:
-  metadata.gz: c3b3e8264c3284d727289be55a71a8f641b801e5610f9261e3caa5d35894fba887d8d23e518e61562751ea25d4d2fcb4a704a0d2132d18e7a0f5fadfedc474df
-  data.tar.gz: 2bab54b8012900039840a4259c4c5cb98378a312f899530825b4743de4bb1c9d344920cb1073a63e057b7e99b19e06c75c001d1f53fb7ba3c559310b48f9b42b
+  metadata.gz: 084c3630e60c5bb99fd839e840c42d0012d647e4f3dd76b2737f979013d09740877aee5900130f59beca69cef1f76cd7a78613edc3d18c43e3879d2d52808af7
+  data.tar.gz: 073011ae6b9398b2b3961374181b5b1ec32711a96b1989bf0bb563b7df26f566442312cf9d64ce0e5824f5a9d835c6f3193b61982a0cec9f5dd72b29b6dc42c3

data/.travis.yml

@@ -1,9 +1,10 @@
 rvm:
   - 1.9.3
   - 2.0.0
-  - 2.1.0
-  - 2.2.2
-  - 2.3.0
+  - 2.1.9
+  - 2.2.5
+  - 2.3.1
+  - ruby-head
   - jruby-19mode
   - rbx-2
 before_install:
@@ -20,17 +21,18 @@ gemfile:
   - gemfiles/5.0.gemfile
 matrix:
   fast_finish: true
-  allow_failures:
-    - rvm: jruby-19mode
-      gemfile: gemfiles/5.0.gemfile
+  exclude:
     - rvm: 1.9.3
       gemfile: gemfiles/5.0.gemfile
     - rvm: 2.0.0
       gemfile: gemfiles/5.0.gemfile
-    - rvm: 2.1.0
+    - rvm: 2.1.9
       gemfile: gemfiles/5.0.gemfile
-    - rvm: rbx-2
+  allow_failures:
+    - rvm: ruby-head
+    - rvm: jruby-19mode
       gemfile: gemfiles/5.0.gemfile
+    - rvm: rbx-2
 branches:
   only:
     - master

data/Appraisals

@@ -15,5 +15,5 @@ appraise '4.2' do
 end
 
 appraise '5.0' do
-  gem 'activerecord', "~> 5.0.0.beta2"
+  gem 'activerecord', "~> 5.0.0"
 end

data/CONTRIBUTING.md

@@ -20,15 +20,25 @@ Here are some ways *you* can contribute:
 [issues]: https://github.com/thoughtbot/factory_girl/issues
 
 ## Submitting an Issue
-We use the [GitHub issue tracker][issues] to track bugs and features. Before
-submitting a bug report or feature request, check to make sure it hasn't
-already been submitted. When submitting a bug report, please include a [Gist][]
-that includes a stack trace and any details that may be necessary to reproduce
-the bug, including your gem version, Ruby version, and operating system.
-Ideally, a bug report should include a pull request with failing specs.
+
+* We use the [GitHub issue tracker][issues] to track bugs and features.
+* Before submitting a bug report or feature request, check to make sure it hasn't
+already been submitted.
+* When submitting a bug report, please include a [Gist][] that includes a stack
+  trace and any details that may be necessary to reproduce the bug, including
+  your gem version, Ruby version, and operating system.  Ideally, a bug report
+  should include a pull request with failing specs.
 
 [gist]: https://gist.github.com/
 
+## Cleaning up issues
+
+* Issues that have no response from the submitter will be closed after 30 days.
+* Issues will be closed once they're assumed to be fixed or answered. If the
+  maintainer is wrong, it can be opened again.
+* If your issue is closed by mistake, please understand and explain the issue.
+  We will happily reopen the issue.
+
 ## Submitting a Pull Request
 1. [Fork][fork] the [official repository][repo].
 2. [Create a topic branch.][branch]
@@ -38,6 +48,8 @@ Ideally, a bug report should include a pull request with failing specs.
 
 ## Notes
 * Please add tests if you changed code. Contributions without tests won't be accepted.
+* If you don't know how to add tests, please put in a PR and leave a comment
+  asking for help. We love helping!
 * Please don't update the Gem version.
 
 [repo]: https://github.com/thoughtbot/factory_girl/tree/master

data/GETTING_STARTED.md

@@ -28,8 +28,9 @@ Once your Gemfile is updated, you'll want to update your bundle.
 Configure your test suite
 -------------------------
 
-```ruby
 # RSpec
+
+```ruby
 # spec/support/factory_girl.rb
 RSpec.configure do |config|
   config.include FactoryGirl::Syntax::Methods
@@ -43,38 +44,56 @@ RSpec.configure do |config|
     FactoryGirl.find_definitions
   end
 end
+```
 
-Remember to require the above file in your spec_helper since the support folder isn't eagerly loaded
+Remember to require the above file in your rails_helper since the support folder isn't eagerly loaded
 
 ```ruby
 require 'support/factory_girl'
 ```
 
 # Test::Unit
+
+```ruby
 class Test::Unit::TestCase
   include FactoryGirl::Syntax::Methods
 end
+```
 
 # Cucumber
+
+```ruby
 # env.rb (Rails example location - RAILS_ROOT/features/support/env.rb)
 World(FactoryGirl::Syntax::Methods)
+```
 
 # Spinach
+
+```ruby
 class Spinach::FeatureSteps
   include FactoryGirl::Syntax::Methods
 end
+```
 
 # Minitest
+
+```ruby
 class Minitest::Unit::TestCase
   include FactoryGirl::Syntax::Methods
 end
+```
 
 # Minitest::Spec
+
+```ruby
 class Minitest::Spec
   include FactoryGirl::Syntax::Methods
 end
+```
 
 # minitest-rails
+
+```ruby
 class ActiveSupport::TestCase
   include FactoryGirl::Syntax::Methods
 end
@@ -151,13 +170,13 @@ user.first_name
 # => "Joe"
 ```
 
-Lazy Attributes
----------------
+Dynamic Attributes
+------------------
 
 Most factory attributes can be added using static values that are evaluated when
 the factory is defined, but some attributes (such as associations and other
 attributes that must be dynamically generated) will need values assigned each
-time an instance is generated. These "lazy" attributes can be added by passing a
+time an instance is generated. These "dynamic" attributes can be added by passing a
 block instead of a parameter:
 
 ```ruby
@@ -179,7 +198,7 @@ end
 
 Aliases
 -------
-FactoryGirl allows you to define aliases to existing factories to make them easier to re-use. This could come in handy when, for example, your Post object has a author attribute that actually refers to an instance of a User class. While normally FactoryGirl can infer the factory name from the association name, in this case it will look for a author factory in vain. So, alias your user factory so it can be used under alias names.
+factory_girl allows you to define aliases to existing factories to make them easier to re-use. This could come in handy when, for example, your Post object has an author attribute that actually refers to an instance of a User class. While normally factory_girl can infer the factory name from the association name, in this case it will look for a author factory in vain. So, alias your user factory so it can be used under alias names.
 
 ```ruby
 factory :user, aliases: [:author, :commenter] do
@@ -207,7 +226,8 @@ end
 Dependent Attributes
 --------------------
 
-Attributes can be based on the values of other attributes using the evaluator that is yielded to lazy attribute blocks:
+Attributes can be based on the values of other attributes using the evaluator
+that is yielded to dynamic attribute blocks:
 
 ```ruby
 factory :user do
@@ -269,6 +289,42 @@ end
 
 ```
 
+Inheritance
+-----------
+
+You can easily create multiple factories for the same class without repeating common attributes by nesting factories:
+
+```ruby
+factory :post do
+  title "A title"
+
+  factory :approved_post do
+    approved true
+  end
+end
+
+approved_post = create(:approved_post)
+approved_post.title    # => "A title"
+approved_post.approved # => true
+```
+
+You can also assign the parent explicitly:
+
+```ruby
+factory :post do
+  title "A title"
+end
+
+factory :approved_post, parent: :post do
+  approved true
+end
+```
+
+As mentioned above, it's good practice to define a basic factory for each class
+with only the attributes required to create it. Then, create more specific
+factories that inherit from this basic parent. Factory definitions are still
+code, so keep them DRY.
+
 Associations
 ------------
 
@@ -372,13 +428,13 @@ create(:user_with_posts).posts.length # 5
 create(:user_with_posts, posts_count: 15).posts.length # 15
 ```
 
-Generating data for a `has_and_belongs_to_many` relationship is very similar 
-to the above `has_many` relationship, with a small change, you need to pass an 
-array of objects to the model's pluralized attribute name rather than a single 
+Generating data for a `has_and_belongs_to_many` relationship is very similar
+to the above `has_many` relationship, with a small change, you need to pass an
+array of objects to the model's pluralized attribute name rather than a single
 object to the singular version of the attribute name.
 
 Here's an example with two models that are related via
- `has_and_belongs_to_many`: 
+ `has_and_belongs_to_many`:
 
 ```ruby
 FactoryGirl.define do
@@ -393,7 +449,7 @@ FactoryGirl.define do
   factory :profile do
     name "John Doe"
 
-    # profile_with_languages will create language data after the profile has 
+    # profile_with_languages will create language data after the profile has
     # been created
     factory :profile_with_languages do
       # languages_count is declared as an ignored attribute and available in
@@ -402,10 +458,10 @@ FactoryGirl.define do
         languages_count 5
       end
 
-      # the after(:create) yields two values; the profile instance itself and 
-      # the evaluator, which stores all values from the factory, including 
-      # ignored attributes; `create_list`'s second argument is the number of 
-      # records to create and we make sure the profile is associated properly 
+      # the after(:create) yields two values; the profile instance itself and
+      # the evaluator, which stores all values from the factory, including
+      # ignored attributes; `create_list`'s second argument is the number of
+      # records to create and we make sure the profile is associated properly
       # to the language
       after(:create) do |profile, evaluator|
         create_list(:language, evaluator.languages_count, profiles: [profile])
@@ -423,42 +479,6 @@ create(:profile_with_languages).languages.length # 5
 create(:profile_with_languages, languages_count: 15).languages.length # 15
 ```
 
-Inheritance
------------
-
-You can easily create multiple factories for the same class without repeating common attributes by nesting factories:
-
-```ruby
-factory :post do
-  title "A title"
-
-  factory :approved_post do
-    approved true
-  end
-end
-
-approved_post = create(:approved_post)
-approved_post.title    # => "A title"
-approved_post.approved # => true
-```
-
-You can also assign the parent explicitly:
-
-```ruby
-factory :post do
-  title "A title"
-end
-
-factory :approved_post, parent: :post do
-  approved true
-end
-```
-
-As mentioned above, it's good practice to define a basic factory for each class
-with only the attributes required to create it. Then, create more specific
-factories that inherit from this basic parent. Factory definitions are still
-code, so keep them DRY.
-
 Sequences
 ---------
 
@@ -482,19 +502,19 @@ generate :email
 # => "person2@example.com"
 ```
 
-Sequences can be used as attributes:
+Sequences can be used in dynamic attributes:
 
 ```ruby
-factory :user do
-  email
+factory :invite do
+  invitee { generate(:email) }
 end
 ```
 
-Or in lazy attributes:
+Or as implicit attributes:
 
 ```ruby
-factory :invite do
-  invitee { generate(:email) }
+factory :user do
+  email # Same as `email { generate(:email) }`
 end
 ```
 
@@ -729,21 +749,37 @@ end
 create(:post).author
 ```
 
-Finally, traits can be used within other traits to mix in their attributes.
+Traits can be used within other traits to mix in their attributes.
 
 ```ruby
-FactoryGirl.define do
-  factory :order do
-    trait :completed do
-      completed_at { 3.days.ago }
+factory :order do
+  trait :completed do
+    completed_at { 3.days.ago }
+  end
+
+  trait :refunded do
+    completed
+    refunded_at { 1.day.ago }
+  end
+end
+```
+
+Finally, traits can accept transient attributes.
+
+```ruby
+factory :invoice do
+  trait :with_amount do
+    transient do
+      amount 1
     end
 
-    trait :refunded do
-      completed
-      refunded_at { 1.day.ago }
+    after(:create) do |invoice, evaluator|
+      create :line_item, invoice: invoice, amount: evaluator.amount
     end
   end
 end
+
+create :invoice, :with_amount, amount: 2
 ```
 
 Callbacks
@@ -901,6 +937,12 @@ To set the attributes for each of the factories, you can pass in a hash as you n
 twenty_year_olds = build_list(:user, 25, date_of_birth: 20.years.ago)
 ```
 
+`build_stubbed_list` will give you fully stubbed out instances:
+
+```ruby
+stubbed_users = build_stubbed_list(:user, 25) # array of stubbed users
+```
+
 There's also a set of `*_pair` methods for creating two records at a time:
 
 ```ruby
@@ -908,6 +950,12 @@ built_users   = build_pair(:user) # array of two built users
 created_users = create_pair(:user) # array of two created users
 ```
 
+If you need multiple attribute hashes, `attributes_for_list` will generate them:
+
+```ruby
+users_attrs = attributes_for_list(:user, 25) # array of attribute hashes
+```
+
 Linting Factories
 -----------------
 
@@ -968,12 +1016,12 @@ FactoryGirl.lint factories_to_lint
 
 This would lint all factories that aren't prefixed with `old_`.
 
-Traits can also be linted. This option verifies that each  
-and every trait of a factory generates a valid object on its own. 
+Traits can also be linted. This option verifies that each
+and every trait of a factory generates a valid object on its own.
 This is turned on by passing `traits: true` to the `lint` method:
 
 ```ruby
-FactoryGirl.lint traits:true
+FactoryGirl.lint traits: true
 ```
 
 This can also be combined with other arguments:
@@ -1276,7 +1324,7 @@ FactoryGirl.define do
     name 'United States'
     association :location_group, factory: :north_america
   end
-  
+
   factory :north_america, class: LocationGroup do
     name 'North America'
   end

data/Gemfile.lock

@@ -1,35 +1,33 @@
 PATH
   remote: .
   specs:
-    factory_girl (4.7.0)
+    factory_girl (4.8.0)
       activesupport (>= 3.0.0)
 
 GEM
   remote: https://rubygems.org/
   specs:
-    activemodel (4.2.5.1)
-      activesupport (= 4.2.5.1)
-      builder (~> 3.1)
-    activerecord (4.2.5.1)
-      activemodel (= 4.2.5.1)
-      activesupport (= 4.2.5.1)
-      arel (~> 6.0)
-    activerecord-jdbc-adapter (1.3.19)
+    activemodel (5.0.0.1)
+      activesupport (= 5.0.0.1)
+    activerecord (5.0.0.1)
+      activemodel (= 5.0.0.1)
+      activesupport (= 5.0.0.1)
+      arel (~> 7.0)
+    activerecord-jdbc-adapter (1.3.21)
       activerecord (>= 2.2)
-    activerecord-jdbcsqlite3-adapter (1.3.19)
-      activerecord-jdbc-adapter (~> 1.3.19)
+    activerecord-jdbcsqlite3-adapter (1.3.21)
+      activerecord-jdbc-adapter (~> 1.3.21)
       jdbc-sqlite3 (>= 3.7.2, < 3.9)
-    activesupport (4.2.5.1)
+    activesupport (5.0.0.1)
+      concurrent-ruby (~> 1.0, >= 1.0.2)
       i18n (~> 0.7)
-      json (~> 1.7, >= 1.7.7)
       minitest (~> 5.1)
-      thread_safe (~> 0.3, >= 0.3.4)
       tzinfo (~> 1.1)
     appraisal (2.1.0)
       bundler
       rake
       thor (>= 0.14.0)
-    arel (6.0.3)
+    arel (7.1.4)
     aruba (0.13.0)
       childprocess (~> 0.5.6)
       contracts (~> 0.9)
@@ -42,6 +40,8 @@ GEM
     builder (3.2.2)
     childprocess (0.5.9)
       ffi (~> 1.0, >= 1.0.11)
+    concurrent-ruby (1.0.2)
+    concurrent-ruby (1.0.2-java)
     contracts (0.13.0)
     cucumber (1.3.20)
       builder (>= 2.1.2)
@@ -62,7 +62,7 @@ GEM
     json (1.8.3)
     json (1.8.3-java)
     metaclass (0.0.4)
-    minitest (5.8.4)
+    minitest (5.9.1)
     mocha (1.1.0)
       metaclass (~> 0.0.1)
     multi_json (1.11.2)
@@ -89,7 +89,7 @@ GEM
       json (~> 1.8)
       simplecov-html (~> 0.10.0)
     simplecov-html (0.10.0)
-    sqlite3 (1.3.11)
+    sqlite3 (1.3.12)
     thor (0.19.1)
     thread_safe (0.3.5)
     thread_safe (0.3.5-java)
@@ -120,4 +120,4 @@ DEPENDENCIES
   yard
 
 BUNDLED WITH
-   1.11.2
+   1.13.6