shoulda-matchers | Simple one-liner tests for common Rails functionality | Application Framework library

You got one of them right, but not the other.

You have spring in your gemfile, usually hanging consoles and servers are related to that. The webrick gem was removed from the standard library in Ruby 3, so that's why it needs to be included in your Gemfile.

Re-add webrick to your Gemfile, do a bundle install, and then stop the background spring server with bin/spring stop. Then re-run the server.

Your best bet on solving issues with spring would be to head over and read about the gem on the GitHub project page, or opening a new question here on SO.

According to this issue on github,

You might want to add this to your spec_helper.rb:

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.

How I solved it:

1. Go to server command line
2. As we can see in error log, the last command before error appears was:

Command: cd /home/deploy/project/releases/20201018151933 && ( export RAILS_ENV="production" RBENV_ROOT="$HOME/.rbenv" RBENV_VERSION="2.6.5" ; RBENV_ROOT=$HOME/.rbenv RBENV_VERSION=2.6.5 $HOME/.rbenv/shims/bundle exec bundle check )

So we go to our folder:

cd /home/deploy/project/releases/20201018151933

and run there command:

export RAILS_ENV="production" RBENV_ROOT="$HOME/.rbenv" RBENV_VERSION="2.6.5" ; RBENV_ROOT=$HOME/.rbenv RBENV_VERSION=2.6.5 $HOME/.rbenv/shims/bundle exec bundle check

After that we see same error:

Could not find concurrent-ruby-1.1.7 in any of the sources. Run 'bundle install' to install missing gems.

1. In same folder run bundle install and after gem installed we can out of server command line.
2. Run cap production deploy and everything is gonna be fine.

I still don't know what is the root problem of this error, and how to fix it permanently, but this works for me. I hope it will be useful for anyone else.

I'll steer away from an opinion on the 'should I...' part, but there are a couple of aspects worth considering. First, although controller tests have not been formally deprecated, they have generally been discouraged by both the Rails and Rspec teams for a while now. From the RSpec 3.5 release notes:

The official recommendation of the Rails team and the RSpec core team is to write request specs instead. Request specs allow you to focus on a single controller action, but unlike controller tests involve the router, the middleware stack, and both rack requests and responses. This adds realism to the test that you are writing, and helps avoid many of the issues that are common in controller specs.

Whether or not the scenario warrants a corresponding request spec is a judgement call, but if you want to unit test the validation at the model level, check out the shoulda matchers gem, which assists with model validation testing).

In terms of your question about hooks, before(:all) hooks run outside a database transaction, so even if you have use_transactional_fixtures set to true in your RSpec configuration, they won't be automatically rolled back. So, a matching after(:all) like you have is the way to go. Alternatives include:

1. Creating the user inside a before(:each) hook, which does run in a transaction and is rolled back. That's at the potential cost of some test performance.
2. Use a tool like the Database Cleaner gem, which gives you fine-grained control over the strategies for cleaning your test databases.

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.

This is by design. When installing Ruby as a system executable (or using the default installer without explicit gem path), the gem path will always use the major Ruby version as the path component for gems. This is so that you can update the minor version without having to reinstall all your gems.

So any 2.6.x version, will have its gems installed in /...something.../2.6.0/gems by default.

This is a different story when using RVM or rbenv, where you can explicitly specify your gemsets for each single Ruby installation. We can see this in your RVM installation, where the gemset path is very specific and tied directly to that particular Ruby executable.

Change

command 'cd /home/sotldirectory && bin/rails r import/cron_import.rb'

to

command 'cd /home/sotldirectory && bundle exec rails r import/cron_import.rb'

Also, which rake version is listed in your Gemfile.lock?