shoulda-matchers VS factory_bot_rails

According to the shoulda-matchers documentation:

The value of shoulda-matchers is right there in the first line of the README: "test common Rails functionality that, if written by hand, would be much longer, more complex, and error-prone."

I work at thoughtbot, you might know us for our open source work like administrate, factory_bot or shoulda-matchers.

4. Shoulda-matchers

While we’re at it, let's add a couple of other gems we’ll need for our test environment: factory_bot_rails is a fixtures replacement and generates test model instances. faker is handy for generating fake strings of data to be used in tests. Add those gems to the development and test group of your Gemfile:

Factory Bot Rails

rspec-rails factory_bot_rails faker

Hey all, just published a simple gem to mass generate FactoryBot factories for existing projects. Someone had this issue on GitHub (https://github.com/thoughtbot/factory_bot_rails/issues/404). I failed to build it in a nice way within the main gem, but wanted to get a solution out there for people who might be in need. I had to get some legacy codebases up to speed in the past, and this would have been useful. Cheers! https://github.com/FanaHOVA/factory_bot_rails_seeder

I use FactoryBot for creating the factory, for stubbing the factory. My factory is containing an image that has to be uploaded and attached as doc every time a factory created:

Here is some real Gherkin from the Factory Bot Rails gem source code on GitHub:

If your are using gems like faker , factory_bot_rails and database_cleaner to create and clean test records then creating unnecessary records can cost you time and speed.