factory_girl_rails creates bad dependancies in rake :environment task about factory_bot_rails

[jferris]

Can you paste the person factory that's causing this issue? I think one possible workaround is to use Factory.define :person instead of Factory.define Person.

I think the issue is that simply referencing the Person class fails if the table doesn't exist yet.

[CodeSturgeon]

Sorry, I just tried to repro this and realized there is an additional step... one of the factories needs to reference another...

Steps to repro...

• rails generate model Person name:string
• rails generate model Hat type:string person_id:integer
• rake db:migrate
• vim app/model/hat.rb (belongs_to :person)
• vim spec/factories.rb (see below)
• rake db:drop
• rake db:setup

factories.rb contents:

Factory.define :person do |p|
  p.name 'frank'
end

Factory.define :hat do |h|
  h.person Factory(:person)
end

Output...

db/test.sqlite3 already exists
db/test.sqlite3 already exists
db/development.sqlite3 already exists
rake aborted!
Could not find table 'people'

[jferris]

Alright, I see the issue. You want to use a dynamic attribute, so that it generates a new person when each hat is created, instead of creating a person when the hat factory is defined:

Factory.define :hat do |h|
  h.person { Factory(:person) }
end

Does that make sense?

[CodeSturgeon]

HA! I just figured out this workaround myself and came to comment. Lazy attributes FTW.

I can see (after some thought) how this works and gets around the problem. However, it's not intuitive. Perhaps you should update the README so others don't stumble in to this trap as I did.

Thanks for the help and the gem in general!

[tsyber1an]

@jferris This was very helpful, thanks