d0208eda9c
Background --- In issues #64 and #66 (from 2010) people expressed surprise that using the `build` strategy would still `create` any associations. I remember being similarly surprised by that behavior when I first started using factory_bot. The main reason for this behavior is to ensure the built instance will be valid if there were any foreign key validations (like `validates_presence_of :user_id`). If we don't save the associations, there won't be any ids present. PR #191 (from 2011) offers a workaround for people who don't want records to be saved automatically. Passing `strategy: :build` (originally `method: :build`, but later renamed) when declaring the association will prevent it from being saved when using `build`. But #191 isn't really a complete solution (as discussed on the PR after it was merged). `strategy: :build` may do the right thing when building objects with the `build` strategy, but it can cause new problems when using the `create` strategy. A better solution would be something like: `strategy: <whatever strategy I was already using>`. PRs #749 and #961 (merged in 2016) introduce something like that, with the `use_parent_strategy` configuration option. With this turned on `build` end up being generally [a little faster][] than `build_stubbed`, since it no longer needs to hit the database for each association. [a little faster]: https://gist.github.com/composerinteralia/d4796df9140f431e36f88dfb6fe9733a I have set `use_parent_strategy` on several projects now. I also added it to suspenders in thoughtbot/suspenders#952. On newer projects I have not run into any problems. On existing projects I have seen the occasional test failure, which are easy enough to fix by changing `build` to `create`. Unfortunately I don't think `use_parent_strategy` is widely known, since it wasn't documented until #1234 (about a month ago). I also learned in #1234 that the `use_parent_strategy` setting gets wiped out with `FactoryBot.reload`, which can be problematic when using factory_bot_rails. To summarize, we have been exploring having a `build` strategy that uses `build` all the way down since 2010, but there still isn't a totally reliable way to get that. This PR --- * Default to using the parent strategy for factory_bot 5, as suggested in #749. * In the original PR for this (#1240) I had removed `use_parent_strategy`, but to make the transition smoother I ended up fixing the reload problem in #1244 Once factory\_bot 5 is released and the dust has settled, it may make sense to deprecate `use_parent_strategy`, and maybe also the strategy option for associations. |
||
|---|---|---|
| features | ||
| gemfiles | ||
| lib | ||
| spec | ||
| .gitignore | ||
| .hound.yml | ||
| .rspec | ||
| .rubocop.yml | ||
| .simplecov | ||
| .travis.yml | ||
| .yardopts | ||
| Appraisals | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| GETTING_STARTED.md | ||
| Gemfile | ||
| Gemfile.lock | ||
| LICENSE | ||
| NAME.md | ||
| NEWS | ||
| README.md | ||
| RELEASING.md | ||
| Rakefile | ||
| cucumber.yml | ||
| factory_bot.gemspec | ||
README.md
factory_bot 
factory_bot 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_bot with Rails, see factory_bot_rails.
Interested in the history of the project name?
Transitioning from factory_girl?
Check out the guide.
Documentation
You should find the documentation for your version of factory_bot on Rubygems.
See GETTING_STARTED for information on defining and using factories. We also have a detailed introductory video, available for free on Upcase.
Install
Add the following line to Gemfile:
gem 'factory_bot'
and run bundle install from your shell.
To install the gem manually from your shell, run:
gem install factory_bot
Supported Ruby versions
The factory_bot 5.x series supports MRI Ruby 2.3+.
The factory_bot 3.x+ series supports MRI Ruby 1.9. Additionally, factory_bot 3.6+ supports JRuby 1.6.7.2+ while running in 1.9 mode. See GETTING_STARTED for more information on configuring the JRuby environment.
For versions of Ruby prior to 1.9, please use factory_bot 2.x.
More Information
You may also find useful information under the factory_girl tag on Stack Overflow.
Contributing
Please see CONTRIBUTING.md.
factory_bot was originally written by Joe Ferris and is now maintained by Josh Clayton. Many improvements and bugfixes were contributed by the open source community.
License
factory_bot is Copyright © 2008-2016 Joe Ferris and thoughtbot. It is free software, and may be redistributed under the terms specified in the LICENSE file.
About thoughtbot
factory_bot is maintained and funded by thoughtbot, inc. The names and logos for thoughtbot are trademarks of thoughtbot, inc.
We love open source software! See our other projects or hire us to design, develop, and grow your product.