Factories from engine not loaded
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- rails, ruby, spring
- Domain
- developer-experience, testing
Research direction
Start with factories.rb and the require of spree/testing_support/factories, then compare factory loading when RSpec or Cucumber runs directly versus through Spring. Reproduce with the listed Ruby, Rails, Spring, and FactoryGirl versions; done means the user factory is registered and usable under Spring as it is in the direct test runs.
Written by the indexing model from the issue text.
Description
On an application that use Spree (for e-commerce), to use the factories, we do in factories.rb :
require "spree/testing_support/factories"
Factories work with launching Rspec and Cucumber directly but with Spring, it fails with:
ArgumentError:
Factory not registered: user
I suspect this is related to engines because on another app with factories from an engine, we have the same error.
Spring 1.3.6
Ruby 2.2.2
Rails 4.2.3
FactoryGirl 4.5.0
- Dominant language
- Ruby
- Stars
- 2.8k
- Forks
- 342
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rails/spring
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 52/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 32/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Similar issues
-
バグ
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
voxpupuli/puppet-epel#186 · 1 comment ·
-
external_created_at is no longer used for the message timestamp since the new message UI (v4.4.0) OpenBug Frontend
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
TheOdinProject/curriculum#31402 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100