factory_girl_kibiz0r 2.0.0.beta2

data/Appraisals

@@ -0,0 +1,12 @@
+appraise "2.1" do
+  gem "activerecord", "~> 2.1"
+end
+
+appraise "2.3" do
+  gem "activerecord", "~> 2.3"
+end
+
+appraise "3.0" do
+  gem "activerecord", "~> 3.0"
+end
+

data/CONTRIBUTION_GUIDELINES.md

@@ -0,0 +1,9 @@
+We're using [GitHub](http://github.com/thoughtbot/factory_girl/tree/master), and we've been getting any combination of github pull requests, patches, emails, etc.  We need to normalize this workflow to make sure we don't miss any fixes.
+
+* Make sure you're accessing the source from the [official repository](http://github.com/thoughtbot/factory_girl/tree/master).
+* Please make a branch for each separate contribution.  We can cherry pick your commits, but pulling from a branch is easier.
+* If you're submitting patches, please cut each fix or feature into a separate patch.
+* There should be an [issue](http://github.com/thoughtbot/factory_girl/issues) for any submission.  If you've found a bug and want to fix it, open a new ticket at the same time.
+* Please <b>don't send pull requests</b>  Just update the issue with the url for your fix when it's ready.  The github pull requests pretty much get dropped on the floor until someone with commit rights notices them in the mailbox.
+* Contributions without tests won't be accepted.
+* Please don't submit patches or branches that update the Gem version.

data/Changelog

@@ -0,0 +1,29 @@
+1.1.4 (November 28, 2008)
+  Factory.build now uses Factory.create for associations of the built object
+  Factory definitions are now detected in subdirectories, such as
+		factories/person_factory.rb (thanks to Josh Nichols)
+  Factory definitions are now loaded after the environment in a Rails project
+		(fixes some issues with dependencies being loaded too early) (thanks to
+		Josh Nichols)
+  Factory names ending in 's' no longer cause problems (thanks to Alex Sharp
+		and Josh Owens)
+  
+1.1.3 (September 12, 2008)
+  Automatically pull in definitions from factories.rb, test/factories.rb, or
+	spec/factories.rb
+1.1.2 (July 30, 2008)
+  Improved error handling for invalid and undefined factories/attributes
+	Improved handling of strings vs symbols vs classes
+	Added a prettier syntax for handling associations
+  Updated documentation and fixed compatibility with Rails 2.1
+
+1.1.1 (June 23, 2008)
+  The attribute "name" no longer requires using #add_attribute
+
+1.1.0 (June 3, 2008)
+	Added support for dependent attributes
+	Fixed the attributes_for build strategy to not build associations
+  Added support for sequences
+
+1.0.0 (May 31, 208)
+  First version

data/GETTING_STARTED.md

@@ -0,0 +1,246 @@
+Getting Started
+===============
+
+Defining factories
+------------------
+
+Each factory has a name and a set of attributes. The name is used to guess the class of the object by default, but it's possible to explicitly specify it:
+
+    # This will guess the User class
+    FactoryGirl.define do
+      factory :user do
+        first_name 'John'
+        last_name  'Doe'
+        admin false
+      end
+  
+      # This will use the User class (Admin would have been guessed)
+      factory :admin, :class => User do
+        first_name 'Admin'
+        last_name  'User'
+        admin true
+      end
+  
+      # The same, but using a string instead of class constant
+      factory :admin, :class => 'user' do
+        first_name 'Admin'
+        last_name  'User'
+        admin true
+      end
+    end
+
+It is highly recommended that you have one factory for each class that provides the simplest set of attributes necessary to create an instance of that class. If you're creating ActiveRecord objects, that means that you should only provide attributes that are required through validations and that do not have defaults. Other factories can be created through inheritance to cover common scenarios for each class.
+
+Attempting to define multiple factories with the same name will raise an error.
+
+Factories can be defined anywhere, but will be automatically loaded if they
+are defined in files at the following locations:
+
+    test/factories.rb
+    spec/factories.rb
+    test/factories/*.rb
+    spec/factories/*.rb
+
+Using factories
+---------------
+
+factory_girl supports several different build strategies: build, create, attributes_for and stub:
+
+    # Returns a User instance that's not saved
+    user = FactoryGirl.build(:user)
+  
+    # Returns a saved User instance
+    user = FactoryGirl.create(:user)
+  
+    # Returns a hash of attributes that can be used to build a User instance:
+    attrs = FactoryGirl.attributes_for(:user)
+  
+    # Returns an object with all defined attributes stubbed out:
+    stub = FactoryGirl.stub(:user)
+
+No matter which strategy is used, it's possible to override the defined attributes by passing a hash:
+
+    # Build a User instance and override the first_name property
+    user = FactoryGirl.build(:user, :first_name => 'Joe')
+    user.first_name
+    # => "Joe"
+
+If repeating "FactoryGirl" is too verbose for you, you can mix the syntax methods in:
+
+    # rspec
+    RSpec.configure do |config|
+      config.include Factory::Syntax::Methods
+    end
+
+    # Test::Unit
+    class Test::Unit::TestCase
+      include Factory::Syntax::Methods
+    end
+
+Lazy 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 block instead of a parameter:
+
+    factory :user do
+      # ...
+      activation_code { User.generate_activation_code }
+    end
+
+Dependent Attributes
+--------------------
+
+Attributes can be based on the values of other attributes using the proxy that is yielded to lazy attribute blocks:
+
+    factory :user do
+      first_name 'Joe'
+      last_name  'Blow'
+      email { "#{first_name}.#{last_name}@example.com".downcase }
+    end
+
+    FactoryGirl.create(:user, :last_name => 'Doe').email
+    # => "joe.doe@example.com"
+
+Associations
+------------
+
+Associated instances can be generated by using the association method when
+defining a lazy attribute:
+
+    factory :post do
+      # ...
+      author
+    end
+
+You can also specify a different factory or override attributes:
+
+    factory :post do
+      # ...
+      association :author, :factory => :user, :last_name => 'Writely'
+    end
+
+The behavior of the association method varies depending on the build strategy used for the parent object.
+
+    # Builds and saves a User and a Post
+    post = FactoryGirl.create(:post)
+    post.new_record?       # => false
+    post.author.new_record # => false
+
+    # Builds and saves a User, and then builds but does not save a Post
+    post = FactoryGirl.build(:post)
+    post.new_record?       # => true
+    post.author.new_record # => false
+
+If the factory name is the same as the association name, the factory name can
+be left out.
+
+Inheritance
+-----------
+
+You can easily create multiple factories for the same class without repeating common attributes by using inheritance:
+
+    factory :post do
+      # the 'title' attribute is required for all posts
+      title 'A title'
+    end
+  
+    factory :approved_post, :parent => :post do
+      approved true
+      # the 'approver' association is required for an approved post
+      association :approver, :factory => :user
+    end
+
+Sequences
+---------
+
+Unique values in a specific format (for example, e-mail addresses) can be
+generated using sequences. Sequences are defined by calling sequence in a
+definition block, and values in a sequence are generated by calling
+Factory.next:
+
+    # Defines a new sequence
+    FactoryGirl.define do
+      sequence :email do |n|
+        "person#{n}@example.com"
+      end
+    end
+  
+    Factory.next :email
+    # => "person1@example.com"
+  
+    Factory.next :email
+    # => "person2@example.com"
+
+Sequences can be used as attributes:
+
+    factory :user do
+      email
+    end
+
+Or in lazy attributes:
+
+    factory :invite do
+      invitee { Factory.next(:email) }
+    end
+
+And it's also possible to define an in-line sequence that is only used in
+a particular factory:
+
+    factory :user do
+      sequence(:email) {|n| "person#{n}@example.com" }
+    end
+
+Callbacks
+---------
+
+Factory_girl makes available three callbacks for injecting some code:
+
+* after_build  - called after a factory is built   (via FactoryGirl.build)
+* after_create - called after a factory is saved   (via FactoryGirl.create)
+* after_stub   - called after a factory is stubbed (via FactoryGirl.stub)
+
+Examples:
+
+    # Define a factory that calls the generate_hashed_password method after it is built
+    factory :user do
+      after_build { |user| generate_hashed_password(user) }
+    end
+
+Note that you'll have an instance of the user in the block.  This can be useful.
+
+You can also define multiple types of callbacks on the same factory:
+
+    factory :user do
+      after_build  { |user| do_something_to(user) }
+      after_create { |user| do_something_else_to(user) }
+    end
+
+Factories can also define any number of the same kind of callback.  These callbacks will be executed in the order they are specified:
+
+    factory :user do
+      after_create { this_runs_first }
+      after_create { then_this }
+    end
+
+Calling FactoryGirl.create will invoke both after_build and after_create callbacks.
+
+Also, like standard attributes, child factories will inherit (and can also define) callbacks from their parent factory.
+
+Alternate Syntaxes
+------------------
+
+Users' tastes for syntax vary dramatically, but most users are looking for a common feature set. Because of this factory_girl supports "syntax layers" which provide alternate interfaces. See Factory::Syntax for information about the various layers available. For example, the Machinist-style syntax is popular:
+
+    require 'factory_girl/syntax/blueprint'
+    require 'factory_girl/syntax/make'
+    require 'factory_girl/syntax/sham'
+  
+    Sham.email {|n| "#{n}@example.com" }
+  
+    User.blueprint do
+      name  { 'Billy Bob' }
+      email { Sham.email }
+    end
+  
+    User.make(:name => 'Johnny')
+

data/Gemfile

@@ -0,0 +1,12 @@
+source "http://rubygems.org"
+gem "cucumber"
+gem "rake"
+gem "rspec", "~> 2.0"
+gem "rcov"
+gem "activerecord", :require => false
+gem "rr"
+gem "sqlite3-ruby", :require => false
+gem "appraisal"
+gem "yard"
+gem "bluecloth"
+

data/Gemfile.lock

@@ -0,0 +1,62 @@
+GEM
+  remote: http://rubygems.org/
+  specs:
+    activemodel (3.0.1)
+      activesupport (= 3.0.1)
+      builder (~> 2.1.2)
+      i18n (~> 0.4.1)
+    activerecord (3.0.1)
+      activemodel (= 3.0.1)
+      activesupport (= 3.0.1)
+      arel (~> 1.0.0)
+      tzinfo (~> 0.3.23)
+    activesupport (3.0.1)
+    appraisal (0.1)
+      bundler
+      rake
+    arel (1.0.1)
+      activesupport (~> 3.0.0)
+    bluecloth (2.0.9)
+    builder (2.1.2)
+    cucumber (0.9.4)
+      builder (~> 2.1.2)
+      diff-lcs (~> 1.1.2)
+      gherkin (~> 2.2.9)
+      json (~> 1.4.6)
+      term-ansicolor (~> 1.0.5)
+    diff-lcs (1.1.2)
+    gherkin (2.2.9)
+      json (~> 1.4.6)
+      term-ansicolor (~> 1.0.5)
+    i18n (0.4.2)
+    json (1.4.6)
+    rake (0.8.7)
+    rcov (0.9.9)
+    rr (1.0.2)
+    rspec (2.1.0)
+      rspec-core (~> 2.1.0)
+      rspec-expectations (~> 2.1.0)
+      rspec-mocks (~> 2.1.0)
+    rspec-core (2.1.0)
+    rspec-expectations (2.1.0)
+      diff-lcs (~> 1.1.2)
+    rspec-mocks (2.1.0)
+    sqlite3-ruby (1.3.2)
+    term-ansicolor (1.0.5)
+    tzinfo (0.3.23)
+    yard (0.6.4)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  activerecord
+  appraisal
+  bluecloth
+  cucumber
+  rake
+  rcov
+  rr
+  rspec (~> 2.0)
+  sqlite3-ruby
+  yard

data/LICENSE

@@ -0,0 +1,19 @@
+Copyright (c) 2008 Joe Ferris and thoughtbot, inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,64 @@
+factory_girl
+============
+
+factory_girl is a fixtures replacement with a straightforward definition syntax, support for multiple build strategies (saved instances, unsaved instances, attribute hashes, and stubbed objects), and support for multiple factories for the same class (user, admin_user, and so on), including factory inheritance.
+
+If you want to use factory_girl with Rails 3, see
+[factory_girl_rails](http://github.com/thoughtbot/factory_girl_rails).
+
+Documentation
+-------------
+
+You should find the documentation for your version of factory_girl on [Rubygems](http://rubygems.org/gems/factory_girl).
+
+See {file:GETTING_STARTED.md} for information on defining and using factories.
+
+Download
+--------
+
+[Github](http://github.com/thoughtbot/factory_girl/tree/master) or
+
+Rubygems:
+    gem install factory_girl
+
+More Information
+----------------
+
+* [Rubygems](http://rubygems.org/gems/factory_girl)
+* [Mailing list](http://groups.google.com/group/factory_girl)
+* [Issues](http://github.com/thoughtbot/factory_girl/issues)
+* [GIANT ROBOTS SMASHING INTO OTHER GIANT ROBOTS](http://giantrobots.thoughtbot.com)
+
+Contributing
+------------
+
+Please read the contribution guidelines before submitting patches or pull requests.
+
+Credits
+-------
+
+factory_girl was written by Joe Ferris with contributions from several authors, including:
+
+* Alex Sharp
+* Eugene Bolshakov
+* Jon Yurek
+* Josh Nichols
+* Josh Owens
+* Nate Sutton
+
+The syntax layers are derived from software written by the following authors:
+
+* Pete Yandell
+* Rick Bradley
+* Yossef Mendelssohn
+
+![thoughtbot](http://thoughtbot.com/images/tm/logo.png)
+
+factory_girl is maintained and funded by [thoughtbot, inc](http://thoughtbot.com/community)
+
+The names and logos for thoughtbot are trademarks of thoughtbot, inc.
+
+License
+-------
+
+factory_girl is Copyright © 2008-2011 Joe Ferris and thoughtbot. It is free software, and may be redistributed under the terms specified in the LICENSE file.

data/Rakefile

@@ -0,0 +1,54 @@
+require 'rubygems'
+require 'bundler/setup'
+require 'rake'
+require 'rcov/rcovtask'
+require 'date'
+require 'rake/gempackagetask'
+require 'rspec/core/rake_task'
+require 'cucumber/rake/task'
+require 'appraisal'
+require 'yard'
+
+desc 'Default: run the specs and features.'
+task :default => 'spec:unit' do
+  system("rake -s appraisal spec:acceptance features;")
+end
+
+namespace :spec do
+  desc "Run unit specs"
+  RSpec::Core::RakeTask.new('unit') do |t|
+    t.pattern = 'spec/{*_spec.rb,factory_girl/**/*_spec.rb}'
+  end
+
+  desc "Run acceptance specs"
+  RSpec::Core::RakeTask.new('acceptance') do |t|
+    t.pattern = 'spec/acceptance/**/*_spec.rb'
+  end
+end
+
+desc "Run the unit and acceptance specs"
+task :spec => ['spec:unit', 'spec:acceptance']
+
+desc 'Performs code coverage on the factory_girl plugin.'
+Rcov::RcovTask.new do |t|
+  t.test_files = FileList['spec/*_spec.rb']
+  t.verbose = true
+end
+
+desc "Clean files generated by rake tasks"
+task :clobber => [:clobber_rcov]
+
+Cucumber::Rake::Task.new(:features) do |t|
+  t.fork = true
+  t.cucumber_opts = ['--format', (ENV['CUCUMBER_FORMAT'] || 'progress')]
+end
+
+eval("$specification = begin; #{IO.read('factory_girl.gemspec')}; end")
+Rake::GemPackageTask.new($specification) do |package|
+  package.need_zip = true
+  package.need_tar = true
+end
+
+YARD::Rake::YardocTask.new do |t|
+end
+

data/features/factory_girl_steps.feature

@@ -0,0 +1,151 @@
+Feature: Use step definitions generated by factories
+
+  Scenario: create a post and verify its attributes
+    Given the following post exists:
+      | Title       | Body                |
+      | a fun title | here is the content |
+    Then I should find the following for the last post:
+      | title       | body                |
+      | a fun title | here is the content |
+
+  Scenario: create a post without a table and verify its attributes
+    Given a post exists with a title of "a fun title"
+    Then I should find the following for the last post:
+      | title       |
+      | a fun title |
+
+  Scenario: flexible English when creating posts
+    Given an post exists with an title of "a fun title"
+    Then I should find the following for the last post:
+      | title       |
+      | a fun title |
+
+  Scenario: create a post with an underscore in an attribute name
+    Given a post exists with an author ID of "5"
+    Then I should find the following for the last post:
+      | author_id |
+      | 5         |
+
+  Scenario: create several posts
+    Given the following posts exist:
+      | Title | Body   |
+      | one   | first  |
+      | two   | second |
+      | three | third  |
+    Then I should find the following for the last post:
+      | title | body  |
+      | three | third |
+    And there should be 3 posts
+
+  Scenario: create a post with a new author
+    Given the following post exists:
+      | Title   | Author   |
+      | a title | ID: 123  |
+    Then I should find the following for the last post:
+      | title   | author_id |
+      | a title | 123       |
+    And I should find the following for the last user:
+      | id  |
+      | 123 |
+
+  Scenario: create a post with an existing author
+    Given the following user exists:
+      | ID  | Name |
+      | 123 | Joe  |
+    And the following post exists:
+      | Title   | Author    |
+      | a title | Name: Joe |
+    Then I should find the following for the last post:
+      | title   | author_id |
+      | a title | 123       |
+    And there should be 1 user
+
+  Scenario: create post with and without a category association
+    Given the following users exist:
+      | ID  | Name |
+      | 123 | Joe  |
+    And the following posts exist:
+      | Title                      | Author    | Category          |
+      | a title                    | Name: Joe | Name: programming |
+      | a title without a category | Name: Joe |                   |
+    Then I should find the following for the last post:
+      | title                      | category_id |
+      | a title without a category |             |
+
+  Scenario: create a user without attributes
+    Given a user exists
+    Then there should be 1 user
+
+  Scenario: create several users without attributes
+    Given 3 users exist
+    Then there should be 3 users
+
+  Scenario: create several users with one attribute
+    Given 3 users exist with a name of "John"
+    Then there should be 3 users
+    And I should find the following for the last user:
+      | name |
+      | John |
+
+  Scenario: create instances of a factory with an underscore in its name
+    Given an admin user exists with a name of "John"
+    Then I should find the following for the last user:
+      | name | admin |
+      | John | true  |
+
+  Scenario: create a several instances of a factory with an underscore in its name
+    Given 3 admin users exist
+    Then I should find the following for the last user:
+      | admin |
+      | true  |
+
+  Scenario: use true values when creating instances
+    Given the following user exists:
+      | name | admin |
+      | Bill | true  |
+    Then I should find the following for the last user:
+      | name | admin |
+      | Bill | true  |
+
+  Scenario: use false values when creating instances
+    Given the following user exists:
+      | name | admin |
+      | Mike | false |
+    Then I should find the following for the last user:
+      | name | admin |
+      | Mike | false |
+
+  Scenario: Properly pluralize words
+    Given the following categories exist:
+      | name       |
+      | Bed        |
+      | Test Drive |
+    And 2 categories exist
+    And 2 categories exist with a name of "Future"
+    Then there should be 6 categories
+
+  Scenario: create a post with an existing category group
+    Given the following category exists:
+      | ID  | name    | category group |
+      | 123 | fiction | Name: books    |
+    And the following post exists:
+      | Title                      | Author    | Category                    |
+      | a title                    | Name: Joe | Category Group: Name: books |
+    Then I should find the following for the last post:
+      | title   | category_id |
+      | a title | 123         |
+
+  Scenario: create a post with an existing category group and a new category
+    Given the following category group exists:
+      | ID  | name  |
+      | 456 | books |
+    And the following post exists:
+      | Title     | Author    | Category                    |
+      | a title   | Name: Joe | Category Group: Name: books |
+    Then I should find the following for the last post:
+      | title   |
+      | a title |
+    And I should find the following for the last category:
+      | category_group_id |
+      | 456               |
+

data/features/step_definitions/database_steps.rb

@@ -0,0 +1,20 @@
+Then /^I should find the following for the last (.*):$/ do |model, table|
+  model_class = model.camelize.constantize
+  last_instance = model_class.last or raise "No #{model.pluralize} exist"
+  table.hashes.first.each do |key, value|
+    last_instance.attributes[key].to_s.should == value
+  end
+end
+
+Then /^there should be (\d+) (.*)$/ do |count, model|
+  model_class = model.singularize.camelize.constantize
+  model_class.count.should == count.to_i
+end
+
+Before do
+  Post.delete_all
+  User.delete_all
+  Category.delete_all
+  CategoryGroup.delete_all
+end
+

data/features/support/env.rb

@@ -0,0 +1,6 @@
+PROJECT_ROOT = File.expand_path(File.join(File.dirname(__FILE__), '..', '..'))
+
+$: << File.join(PROJECT_ROOT, 'lib')
+
+require 'active_record'
+require 'factory_girl'