rspec-mocks | RSpec 's 'test double ' framework , with support | Unit Testing library

You're mocking File.exists? and calling File.exist?.

Note that if you have verify_partial_doubles set, and you should, RSpec won't allow you to mock a method which does not exist.

Just stub the method on the instance instead of the class:

I have answered question 1 myself. If anyone else can give me a definitive answer to part two, I will happily mark that as the answer.

I guessed that I needed to download and install the mingw packages that couldn't be downloaded somewhere. I did a bit of trawling and found this article (Offline installation of packages)which gave me the pointers I needed. I got these four files from https://repo.msys2.org/mingw/mingw64/:

From the Yard documentation:

instance_double(doubled_class, stubs)

Parameters:

• doubled_class (String, Class)
• stubs (Hash) — hash of message/return-value pairs

is_happy: true will make the double return true when sent the the message is_happy.

RSpec has both the normal API documentation which is generated by Yard from the code and the guide style documenation that you have linked. Its quite common to have both in a well documented project since they serve different purposes.

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.

Upgrade all gems that are mentioned and might collide with their required RSpec-version. The output tells you, that guard-rspec collides with a newer RSpec-version. Try with:

It seems that you have a cache configuration issue with stimulus_reflex gem when you run the rspec command:

Stimulus Reflex requires caching to be enabled. Caching allows the session to be modified during ActionCable requests. To enable caching in development, run: rails dev:cache

If you know what you are doing and you want to start the application anyway, you can create a StimulusReflex initializer with the command:

bundle exec rails generate stimulus_reflex:config

Then open your initializer at

/config/initializers/stimulus_reflex.rb

and then add the following directive:

StimulusReflex.configure do |config| config.on_failed_sanity_checks = :warn end

No examples found.

Try replacing this part of config/environments/test.rb:

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

Looks like you're running into compatibility issues trying to use the latest version of the activerecord-import gem at the time of writing (released in October 2020) with activerecord 3.2.22.5 (released in September 2016). You do mention it's a rails 3.2.15 app but you're not using activerecord 3.2.15 which is confusing.

Try using activerecord-import 0.4.1 (released in July 2013) and activerecord 3.2.15 which should be compatible with rails 3.2.15.