SimpleCov VS factory_bot_rails

gem "simplecov" - https://github.com/simplecov-ruby/simplecov | Gather spec coverage stats locally and on CI, aim for those 90+%.

Have you wondered how much of the logic in your views is exercised in your test suite? Thanks to this change, now you can see that in tools like SimpleCov.

My talk is about different best practices - specifically when adhering to them breaks down. One of those best practices is high test coverage. I start to work on the content for my presentation by building the code samples that I want to use in the slides. For the code coverage section, I'm writing some code with some tests. I'm using SimpleCov to generate code coverage results.

SimpleCov - a tool to check Ruby application code coverage. You can configure it to run alongside your tests. It provides metrics on code coverage so that you can identify what you need to pay attention to and where to invest your time to create better test cases.

Ensure that you have sufficient test coverage. You can use code coverage analysis tools like SimpleCov to gain insight into gaps in your coverage.

simplecov might the answer you need, it generates a report of the lines of code your test suite hits.

Use SimpleCov to generate a report of how many statements are covered by your test suite. It won't assess the test suite quality, though.

There are many tools for measuring test coverage, but one is SimpleCov. It also supports branches coverage. To measure coverage of production code, check out Coverband, which you can set up to use oneshot lines mode.

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.