factory_bot_rails VS rspec-rails

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.

When starting a Rails project, you have a lot of decisions to make. Whether or not to write tests should not be one of them. The big decision is to use Minitest or Rspec. Both of those testing frameworks are great and provide everything you need to test a Rails application thoroughly.

RSpec

rspec-rails factory_bot_rails faker

Ruby testing with RSpec

After all requests have been added, we need to cover them using request specs to ensure that everything will work as expected in the future as well. To add specs, we will use the rspec-rails gem. Our plan is to cover the 4 HTTP request methods that have been added above:

as a beginner you can skip it, just focus on understanding Rails' philosophy and getting comfortable with it. However, make sure you remember to come back to unit testing later bc it's a mandatory skill for a Rails developer. Unit test can help you understand your project's specs thoroughly (assume its test coverage is more than 90%). I recommend learning RSpec instead of Rails' built-in testing tool (the one being used in the Rails tutorial iirc)

RSpec is a testing framework for Ruby that is widely used in the Ruby on Rails community. It allows developers to write and execute automated tests. RSpec promotes behavior-driven development (BDD) by providing a readable syntax for describing the expected behavior of the application.

This is where rswag comes in. It is an extension to rspec-rails for "describing and testing API operations".