rspec-expectations | readable API to express expected outcomes

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.

Solved by following the steps at https://stackoverflow.com/a/48312139/13217139 then re-installed the gem with gem install ffi -- --enable-system-libffi

The reason why you get a test_helper.rb file instead of an spec_helper.rb file is because rails comes with Minitest as the default framework to write the tests, on the other hand rails has the possibility to use other testing frameworks as Rspec installing it as you mentioned.

In the case, for example of https://github.com/chrisalley/pundit-matchers it says that is a set of RSpec matchers for testing Pundit, so in this case you need to use Rspec in order to use this matchers. If you want to keep using Minitest you probably have to look to a similar option of matchers but for Minitest.

Wether if Rspec or Minispec is better depends on the different aspects of the project and the organizations but both options are powerful options to write tests.

There are more articles in Stack Overflow related to the configuration in Rspec and Minitest, for example:

How is spec/rails_helper.rb different from spec/spec_helper.rb? Do I need it?.

You can also take a look at the documentation for both Rspec and Minitest.

There are also tools to transform your Minitest files to Rspec files like:

https://github.com/jaredbeck/minitest_to_rspec

There may be one culprit gem here but you will run into this problem again and again unless you fix your underlying approach.

Look at your gems environment; all gems are installed into one folder, regardless of the project you’re working on. So, if you have two projects with conflicting dependencies you will get this problem again.

There are tools, like RVM, which let you create environments for each project. So, each project has its own separate collection of gems and even distinct versions of Ruby if you need 2.7 in one project and 2.5 for another.

See "Easy way to setting Ruby Version Manager (RVM) on projects" for how to use RVM and create a gemset for each project.

I think I see what's going on. In your Dockerfile, change your DB_URL from: mysql:// to mysql2://

You are loading the mysql2 gem, but indicating to ActiveRecord that you want to use a connection via the mysql gem.

When you require 'sinatra' certain magic things happen that brings a bunch of stuff into scope and essentially turns your app.rb into an instance of Sinatra::Application. The cookies method is only defined on instances like this – it isn’t present on other classes automatically.

What you probably want to do is turn your helper into a real Sinatra style helper by making it a module and then loading it using the helpers keyword, which will just make these instance methods:

At the moment RubyMine doesn't have support for it. Please add your vote and follow the corresponding request:

https://youtrack.jetbrains.com/issue/RUBY-26444

This is probably and error with the stylesheet_link_tag and stylesheet_pack_tag, check out your layout files probably you are including sass files and you are using stylesheet_link_tag, this is breaking your code given that as I understand you can just link plane css files. so if you are including sass files use the stylesheet_pack_tag