-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rspec issue: no master blueprint defined #108
Comments
If it only happens when many examples are run together, and you're using spork, it's almost certainly a code reloading issue. I'd guess the issue is that the already-defined blueprints don't match against the newly reloaded User class, which is a new object with no relation to the old one. If you can find a smallish set of examples that consistently produce the error, try running them without spork. |
That makes sense, and I took a stroll through the source code to see if they had a I wanted an automatic way to see what classes have blueprints enabled and then iterate through them, doing a
Which appears to work in the console, but I can't get it running in |
I am trying to find a solution for this as well, if anyone comes up with a nice way to reload them just as FactoryGirl.reload does it, please let us know :) |
I keep getting this intermittent error:
When I have clearly defined the blueprints and spork has loaded them. It pops up on capybara specs more than any others, though I have had it pop up on some non-integration specs. I can't seem to find a consistent way to replicate it. Sometimes I'll run a spec in isolation and it will work fine, but when I run the suite, it will break. Sometimes an individual spec will break it. It's quite strange.
Can I get some help tracking this issue down? Pointers?
Thanks!
The text was updated successfully, but these errors were encountered: