factory_bot | A library for setting up Ruby objects as test data | Application Framework library

Thanks for clarifying. If I understood correctly here my take on it.

partials are not not available in a host app as the engine has already compiled them

Partials are still there, precompilation just outputs *.{css/js} files into public/assets/ that are declared in app/assets/config/manifest.js.

To get to engines files, instead of Rails.root use:

spec folder is not in your load_path. You can either:

• use absolute path require Rails.root.join('support/geocoder_helper')

• use relative require require_relative '../support/geocoder_helper'

• add spec folder to your load (in spec_helper.rb): $LOAD_PATH << Rails.root.join('spec')

• require all your support files in spec_helper, which is pretty standard procedure

Other issues: do not define methods on main object. It is quite a terrible practice that I keep fixing in most of the specs, causing a lot of really odd behaviours and subtle bugs. Once the geocoder_helper file is loaded, add_geocoder_stub method is defined on Object class making it available in every single object globally (that is including nil, true, all symbols etc). This is just, well, yucky - not to mention it might cause unexpected behaviour changes as suddenly respond_to? will return true and you just don't know what other libraries might be using this.

Instead, wrap your method in modules:

The issue was related to environment variables and not being able to find the correct path for the gems. I found a solution and updated the schedule.rb file.

There must be a validation in your user model that prevents you from creating users with an email and/or username that's already in the database. And as you have a factory (favorite), that attempts to create a user and a game, without checking first if the user email and/or username already exist, it fails because it uses the values you set for them, which are always the same ("test@gmail.com", "test", correspondingly).

You can use a FactoryBot sequence for that:

I'm not really sure what happened and why but I tried doing this on my rails container and I was no longer receiving the said error.

1. docker-compose run --rm bash
2. cd to project directory
3. bundle install

Make sure to use initialize_with in your factory, so when assigning the attributes, your association is already defined.

Turns out this was being caused by the automatic generation of enum traits, which is why there were those incompatible traits that were causing the linter to fail. The feature is described here, you can disable it with FactoryBot.automatically_define_enum_traits = false (I created a factory_bot.rb file in my initializers directory and disabled it there).

A handler is a class, so just need to do something like this...

You should require 'rails_helper' in your rspec tests, not spec_helper.

rails_helper will set up the rails environment for rspec and load spec_helper, but spec_helper does not load rails_helper. Without rails_helper, rspec does not know how to load the Rails code.