rails５でRspec実行時にエラーが出る

Question

前提・実現したいこと

rails５でRspecを動かしたいのですが

＄bundle exec rspec spec/system/tasks_spec.rb実行後

0 examples, 0 failures, 1 error occurred outside of examples

とエラーが出ます。
試したこと

cannot load such file rails_helperが発生した時に疑うことを参考に

$ rails g rspec:install実行
実行時すでにファイルがあるのでコンフリクトが発生する

Running via Spring preloader in process 16108
   identical  .rspec
       exist  spec
    conflict  spec/spec_helper.rb
Overwrite /Users/user/rails/taskleaf/spec/spec_helper.rb? (enter "h" for help) [Ynaqdhm] yes
       force  spec/spec_helper.rb
   identical  spec/rails_helper.rb

spec/rails_helper.rb

# This file is copied to spec/ when you run 'rails generate rspec:install'
require 'spec_helper'
ENV['RAILS_ENV'] ||= 'test'

require File.expand_path('../config/environment', __dir__)

# Prevent database truncation if the environment is production
abort("The Rails environment is running in production mode!") if Rails.env.production?
require 'rspec/rails'
# Add additional requires below this line. Rails is not loaded until this point!

# Requires supporting ruby files with custom matchers and macros, etc, in
# spec/support/ and its subdirectories. Files matching `spec/**/*_spec.rb` are
# run as spec files by default. This means that files in spec/support that end
# in _spec.rb will both be required and run as specs, causing the specs to be
# run twice. It is recommended that you do not name files matching this glob to
# end with _spec.rb. You can configure this pattern with the --pattern
# option on the command line or in ~/.rspec, .rspec or `.rspec-local`.
#
# The following line is provided for convenience purposes. It has the downside
# of increasing the boot-up time by auto-requiring all files in the support
# directory. Alternatively, in the individual `*_spec.rb` files, manually
# require only the support files necessary.
#
# Dir[Rails.root.join('spec', 'support', '**', '*.rb')].each { |f| require f }

# Checks for pending migrations and applies them before tests are run.
# If you are not using ActiveRecord, you can remove these lines.
begin
  ActiveRecord::Migration.maintain_test_schema!
rescue ActiveRecord::PendingMigrationError => e
  puts e.to_s.strip
  exit 1
end
RSpec.configure do |config|
  # Remove this line if you're not using ActiveRecord or ActiveRecord fixtures
  config.fixture_path = "#{::Rails.root}/spec/fixtures"

  # If you're not using ActiveRecord, or you'd prefer not to run each of your
  # examples within a transaction, remove the following line or assign false
  # instead of true.
  config.use_transactional_fixtures = true

  # RSpec Rails can automatically mix in different behaviours to your tests
  # based on their file location, for example enabling you to call `get` and
  # `post` in specs under `spec/controllers`.
  #
  # You can disable this behaviour by removing the line below, and instead
  # explicitly tag your specs with their type, e.g.:
  #
  #     RSpec.describe UsersController, :type => :controller do
  #       # ...
  #     end
  #
  # The different available types are documented in the features, such as in
  # https://relishapp.com/rspec/rspec-rails/docs
  config.infer_spec_type_from_file_location!

  # Filter lines from Rails gems in backtraces.
  config.filter_rails_from_backtrace!
  # arbitrary gems may also be filtered via:
  # config.filter_gems_from_backtrace("gem name")
end

spec/system/task_spec.rb

require 'rails_helper'

describe 'タスク管理機能', type: :system do
  describe '一覧機能' do
    before do
      # ユーザーAを作成しておく
      user_a = FactoryBot.create(:user, name: 'ユーザーA', email: '[e-mail]')
      # 作成者がユーザーAであるタスクを作成しておく
      FactoryBot.create(:task, name: '最初のタスク', user: user_a)
    end
    context 'ユーザーAがログインしている時' do
      before do
        # ユーザーAでログインする
        visit login_path
        fill_in 'メールアドレス', with: '[e-mail]'
        fill_in 'パスワード', with: 'password'
        click_button 'ログインする'
      end

      it 'ユーザーAが作成したタスクが表示される' do
        # 作成済みのタスクの名称が画面上に表示されていることを確認
        expect(page).to have_content '最初のタスク'
      end
    end

    context 'ユーザーBがログインしている時' do
      before do
        # ユーザーBを作成しておく
        FactoryBot.create(:user, name: 'ユーザーB', email: '[e-mail]')
        # ユーザーBでログインする
        visit.login_path
        fill_in 'メールアドレス', with: '[e-mail]'
        fill_in 'パスワード', with: 'password'
        click_button 'ログインする'
      end

      it 'ユーザーAが作成したタスクが表示されない' do
        # ユーザーAが作成したタスクの名称が画面上に表示されていないことを確認
        expect(page).not_to have_content '最初のタスク'
      end
    end
  end
end

spec/spec_helper.rb

〜省略〜
# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
RSpec.configure do |config|
  # rspec-expectations config goes here. You can use an alternate
  # assertion/expectation library such as wrong or the stdlib/minitest
  # assertions if you prefer.
  config.expect_with :rspec do |expectations|
    # This option will default to `true` in RSpec 4. It makes the `description`
    # and `failure_message` of custom matchers include text for helper methods
    # defined using `chain`, e.g.:
    #     be_bigger_than(2).and_smaller_than(4).description
    #     # => "be bigger than 2 and smaller than 4"
    # ...rather than:
    #     # => "be bigger than 2"
    expectations.include_chain_clauses_in_custom_matcher_descriptions = true
  end

  # rspec-mocks config goes here. You can use an alternate test double
  # library (such as bogus or mocha) by changing the `mock_with` option here.
  config.mock_with :rspec do |mocks|
    # Prevents you from mocking or stubbing a method that does not exist on
    # a real object. This is generally recommended, and will default to
    # `true` in RSpec 4.
    mocks.verify_partial_doubles = true
  end

  # This option will default to `:apply_to_host_groups` in RSpec 4 (and will
  # have no way to turn it off -- the option exists only for backwards
  # compatibility in RSpec 3). It causes shared context metadata to be
  # inherited by the metadata hash of host groups and examples, rather than
  # triggering implicit auto-inclusion in groups with matching metadata.
  config.shared_context_metadata_behavior = :apply_to_host_groups

# The settings below are suggested to provide a good initial experience
# with RSpec, but feel free to customize to your heart's content.
=begin
  # This allows you to limit a spec run to individual examples or groups
  # you care about by tagging them with `:focus` metadata. When nothing
  # is tagged with `:focus`, all examples get run. RSpec also provides
  # aliases for `it`, `describe`, and `context` that include `:focus`
  # metadata: `fit`, `fdescribe` and `fcontext`, respectively.
  config.filter_run_when_matching :focus

  # Allows RSpec to persist some state between runs in order to support
  # the `--only-failures` and `--next-failure` CLI options. We recommend
  # you configure your source control system to ignore this file.
  config.example_status_persistence_file_path = "spec/examples.txt"

  # Limits the available syntax to the non-monkey patched syntax that is
  # recommended. For more details, see:
  #   - http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax/
  #   - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
  #   - http://rspec.info/blog/2014/05/notable-changes-in-rspec-3/#zero-monkey-patching-mode
  config.disable_monkey_patching!

  # Many RSpec users commonly either run the entire suite or an individual
  # file, and it's useful to allow more verbose output when running an
  # individual spec file.
  if config.files_to_run.one?
    # Use the documentation formatter for detailed output,
    # unless a formatter has already been configured
    # (e.g. via a command-line flag).
    config.default_formatter = "doc"
  end

  # Print the 10 slowest examples and example groups at the
  # end of the spec run, to help surface which specs are running
  # particularly slow.
  config.profile_examples = 10

  # Run specs in random order to surface order dependencies. If you find an
  # order dependency and want to debug it, you can fix the order by providing
  # the seed, which is printed after each run.
  #     --seed 1234
  config.order = :random

  # Seed global randomization in this process using the `--seed` CLI option.
  # Setting this allows you to use `--seed` to deterministically reproduce
  # test failures related to randomization by passing the same `--seed` value
  # as the one that triggered the failure.
  Kernel.srand config.seed
=end
end

group :test do
  # Adds support for Capybara system testing and selenium driver
  gem 'capybara', '>= 2.15'
  gem 'selenium-webdriver'
  # Easy installation and use of chromedriver to run system tests with Chrome
  gem 'chromedriver-helper'
  gem 'rspec-rails', '~> 3.7'
end

解決方法が分かりません。
どなたか教えていただけますでしょうか。よろしくお願いします。

Comments

[winterboum]

エラーメッセージってその１行では無いですよね？
そちらにも重要な情報が入っているので、もれなく開示して下さい

[rieru]

winterboumさん、失礼しました。
文字数の関係で追加できませんでしたので、こちらに追加いたしました。
↓以下がエラーメッセージの全文になります。よろしくお願いいたします。

User:system user$ bundle exec rspec spec/system/tasks_spec.rb

An error occurred while loading ./spec/system/tasks_spec.rb.
Hint: Install the `did_you_mean` gem in order to provide suggestions for similarly named files.
Failure/Error: __send__(method, file)

LoadError:
cannot load such file -- /Users/user/rails/taskleaf/spec/system/spec/system/tasks_spec.rb
# /Users/user/rails/taskleaf/vendor/bundle/ruby/2.6.0/gems/rspec-core-3.9.0/lib/rspec/core/configuration.rb:2076:in `load'
# /Users/user/rails/taskleaf/vendor/bundle/ruby/2.6.0/gems/rspec-core-3.9.0/lib/rspec/core/configuration.rb:2076:in `load_file_handling_errors'
# /Users/user/rails/taskleaf/vendor/bundle/ruby/2.6.0/gems/rspec-core-3.9.0/lib/rspec/core/configuration.rb:1583:in `block in load_spec_files'
# /Users/user/rails/taskleaf/vendor/bundle/ruby/2.6.0/gems/rspec-core-3.9.0/lib/rspec/core/configuration.rb:1581:in `each'
# /Users/user/rails/taskleaf/vendor/bundle/ruby/2.6.0/gems/rspec-core-3.9.0/lib/rspec/core/configuration.rb:1581:in `load_spec_files'
# /Users/user/rails/taskleaf/vendor/bundle/ruby/2.6.0/gems/rspec-core-3.9.0/lib/rspec/core/runner.rb:102:in `setup'
# /Users/user/rails/taskleaf/vendor/bundle/ruby/2.6.0/gems/rspec-core-3.9.0/lib/rspec/core/runner.rb:86:in `run'
# /Users/user/rails/taskleaf/vendor/bundle/ruby/2.6.0/gems/rspec-core-3.9.0/lib/rspec/core/runner.rb:71:in `run'
# /Users/user/rails/taskleaf/vendor/bundle/ruby/2.6.0/gems/rspec-core-3.9.0/lib/rspec/core/runner.rb:45:in `invoke'
# /Users/user/rails/taskleaf/vendor/bundle/ruby/2.6.0/gems/rspec-core-3.9.0/exe/rspec:4:in `<top (required)>'
# /Users/user/rails/taskleaf/vendor/bundle/ruby/2.6.0/bin/rspec:23:in `load'
# /Users/user/rails/taskleaf/vendor/bundle/ruby/2.6.0/bin/rspec:23:in `<top (required)>'
# /Users/user/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/cli/exec.rb:74:in `load'
# /Users/user/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/cli/exec.rb:74:in `kernel_load'
# /Users/user/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/cli/exec.rb:28:in `run'
# /Users/user/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/cli.rb:465:in `exec'
# /Users/user/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
# /Users/user/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
# /Users/user/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor.rb:387:in `dispatch'
# /Users/user/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/cli.rb:27:in `dispatch'
# /Users/user/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor/base.rb:466:in `start'
# /Users/user/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/cli.rb:18:in `start'
# /Users/user/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/exe/bundle:30:in `block in <top (required)>'
# /Users/user/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/friendly_errors.rb:124:in `with_friendly_errors'
# /Users/user/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/exe/bundle:22:in `<top (required)>'
# /Users/user/.rbenv/versions/2.6.3/bin/bundle:23:in `load'
# /Users/user/.rbenv/versions/2.6.3/bin/bundle:23:in `<main>'
#
# Showing full backtrace because every line was filtered out.
# See docs for RSpec::Configuration#backtrace_exclusion_patterns and
# RSpec::Configuration#backtrace_inclusion_patterns for more information.
No examples found.

Finished in 0.00005 seconds (files took 0.35676 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples

Answer 1

それはrspecがかわいそう。
Rails.root でbundle exec rspec spec/system/tasks_spec.rb
して下さい

Comments

[rieru]

ありがとうございます。
>それはrspecがかわいそう。
　パスを間違えていたのですね。

ご教授いただいた通りにRails.rootのUsers/user/rails/taskleafで
`$ bundle exec rspec spec/system/tasks_spec.rb`を実行しました。

その結果`Failure/Error: require File.expand_path('../config/environment', __dir__)`が出てしまいました。

　[RubyのFile.expand_path('相対パス', __FILE__)の意味](https://maeharin.hatenablog.com/entry/20130104/p1)を参考にし、File.expand_path('相対パス', __FILE__)は相対パスを絶対パスに変換した文字列を返すと理解しました。

重ねての質問で申し訳ないのですが、現在のディレクトリUsers/user/rails/taskleafから
`../config/environment`を探して、`No examples found.`となっているということでしょうか。
（最初の問題とまた別の問題でしたら別に質問を立てます。。。）

↓以下エラー文です。
An error occurred while loading ./spec/system/tasks_spec.rb.
Failure/Error: require File.expand_path('../config/environment', __dir__)

NameError:
uninitialized constant BetterErrors
# ./vendor/bundle/ruby/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:79:in `block in load_missing_constant'
# ./vendor/bundle/ruby/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:8:in `without_bootsnap_cache'
# ./vendor/bundle/ruby/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:79:in `rescue in load_missing_constant'
# ./vendor/bundle/ruby/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:58:in `load_missing_constant'
# ./config/initializers/better_errors.rb:1:in `<main>'
# ./vendor/bundle/ruby/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:54:in `load'
# ./vendor/bundle/ruby/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:54:in `load'
# ./vendor/bundle/ruby/2.6.0/gems/railties-5.2.4/lib/rails/engine.rb:663:in `block in load_config_initializer'
# ./vendor/bundle/ruby/2.6.0/gems/activesupport-5.2.4/lib/active_support/notifications.rb:170:in `instrument'
# ./vendor/bundle/ruby/2.6.0/gems/railties-5.2.4/lib/rails/engine.rb:662:in `load_config_initializer'
# ./vendor/bundle/ruby/2.6.0/gems/railties-5.2.4/lib/rails/engine.rb:620:in `block (2 levels) in <class:Engine>'
# ./vendor/bundle/ruby/2.6.0/gems/railties-5.2.4/lib/rails/engine.rb:619:in `each'
# ./vendor/bundle/ruby/2.6.0/gems/railties-5.2.4/lib/rails/engine.rb:619:in `block in <class:Engine>'
# ./vendor/bundle/ruby/2.6.0/gems/railties-5.2.4/lib/rails/initializable.rb:32:in `instance_exec'
# ./vendor/bundle/ruby/2.6.0/gems/railties-5.2.4/lib/rails/initializable.rb:32:in `run'
# ./vendor/bundle/ruby/2.6.0/gems/railties-5.2.4/lib/rails/initializable.rb:61:in `block in run_initializers'
# ./vendor/bundle/ruby/2.6.0/gems/railties-5.2.4/lib/rails/initializable.rb:50:in `each'
# ./vendor/bundle/ruby/2.6.0/gems/railties-5.2.4/lib/rails/initializable.rb:50:in `tsort_each_child'
# ./vendor/bundle/ruby/2.6.0/gems/railties-5.2.4/lib/rails/initializable.rb:60:in `run_initializers'
# ./vendor/bundle/ruby/2.6.0/gems/railties-5.2.4/lib/rails/application.rb:361:in `initialize!'
# ./config/environment.rb:5:in `<top (required)>'
# ./spec/rails_helper.rb:5:in `require'
# ./spec/rails_helper.rb:5:in `<top (required)>'
# ./spec/system/tasks_spec.rb:1:in `require'
# ./spec/system/tasks_spec.rb:1:in `<top (required)>'
# ------------------
# --- Caused by: ---
# NameError:
# uninitialized constant BetterErrors
# ./vendor/bundle/ruby/2.6.0/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:60:in `block in load_missing_constant'
No examples found.

[winterboum]

目が疲れてて、読むの辛いので
require File.expand_path('../config/environment', __dir__)`
が書かれているfileは何でしょう。　Rails.rootからの相対PATHで教えて下さい

[rieru]

すみません。。。
require File.expand_path('../config/environment', __dir__)`が書かれているfileはspec/rails_helper.rbです。
```
1 # This file is copied to spec/ when you run 'rails generate rspec:install'
2 require 'spec_helper'
3 ENV['RAILS_ENV'] ||= 'test'
4
5 require File.expand_path('../config/environment', __dir__)
（省略）
```
５行目に書かれていました。読み込もうとしている階層が違うのでしょうか。。。

[winterboum]

spec/rails_helper.rb　があるのは ./spec なので、../config/environment　で合ってますね
ただ変なのは require してるので、dir を返す ', __dir__ が？？？
rspec_rails は手を入れてますか、 もとのまま？
もう一度作りなおすとどうなるか

[rieru]

rspec_railsは手を加えてないです。。。
(https://qiita.com/sys_cat/items/16d55e7cd8a3f177863a)の手順に沿ってgem rspec_railsをアンインストール→インストールし、
・spec/factories/users.rb
・spec/factories/tasks.rb
・spec/system/tasks_spec.rb
のファイルを再度作り直したのですが、またもや`Failure/Error: require File.expand_path('../config/environment', __dir__)`のエラーが出てしまいました。

[winterboum]

rails g rspec:install
はやり直してみましたか？

[rieru]

遅くなりすみません。再度gemのインストール、rails g rspec:installもやり直してみましたがエラーになってしまいました。

Answer 2

/Users/user/rails/taskleaf　と言うのはテスト対象のRailアプリケーションのRails.rootでしょうか？
そこに　spec/system/spec/system/tasks_spec.rb　がないと言っています。「ない」じゃないな　Load出来ない。
ん？　なんか変ですね。spec/system がダブってる。

確認

1. bundle exec rspec　を行った directory はどこですか
2. そこから spec/system/spec/system/tasks_spec.rb に向かってどこまで存在しますか
3. bundle exec rspec tasks_spec.rb とすると

LoadError:
cannot load such file -- /Users/user/rails/taskleaf/spec/system/spec/system/tasks_spec.rb

エラーメッセージのこの辺りはどう変わりますか

Comments

[rieru]

情報が不十分で申し訳ないです。
>/Users/user/rails/taskleaf　と言うのはテスト対象のRailアプリケーションのRails.rootでしょうか？
そうです。taskleafというRailアプリケーションです。

1) bundle exec rspec　を行った directory はどこですか
　`$ pwd`コマンド実行結果
/Users/useri/rails/taskleaf/spec/system

2) そこから spec/system/spec/system/tasks_spec.rb に向かってどこまで存在しますか

`$ ls`実行後存在するファイルは以下の通りでした。
tasks_spec.rb

3) bundle exec rspec tasks_spec.rb とすると
`$ bundle exec rspec tasks_spec.rb`実行後のエラーメッセージは`LoadError`ではなくなりました。
↓エラーメッセージ
bash: bundle exec rspec tasks_spec.rb: command not found