常連

### 前提・実現したいこと


現在、Railsを勉強しています。
現場で使えるRuby on Rails 5 速習実践ガイドという教材を進めています。
aws cloud9 を使ってRailsTutorialをしていたため、そのままawsで勉強を続けています。

その中で、新しくRSpecを用いてコードを書いています。
テストを作成し、rspecを実行したところで以下のエラーメッセージが出ました。


### 発生している問題・エラーメッセージ

```
Selenium::WebDriver::Error::UnknownError: unknown error: cannot find Chrome binary

```
これについては以下のページの内容を参考にしました。
参考: https://kuracux.hatenablog.jp/entry/2018/12/30/182617
Amazon LinuxにChromeが入っていないことが原因だと考えられます。
下記コマンドを実行し、インストールを行ないましょう。

$ curl https://intoli.com/install-google-chrome.sh | bash

これで解決したと思ったのですが、この後再度rspecを実行すると、

```
Selenium::WebDriver::Error::SessionNotCreatedError:
session not created: This version of ChromeDriver only supports Chrome version 74
(Driver info: chromedriver=74.0.3729.6 (255758eccf3d244491b8a1317aa76e1ce10d57e9-refs/branch-heads/3729@{#29}),platform=Linux 4.14.97-74.72.amzn1.x86_64 x86_64)
```
と出て、テストが実行できず、詰まってしまいました。


### 試したこと
エラー文から察するに
chromedriverとChromeのバージョンが違うので、それをあわせることが必要という解釈をしました。
自分なりに調べて、以下のページなどを参考に、Chromeのバージョンを74にあげる方法を模索しましたが、できませんでした。


参考：CircleCIのChromeとchromedriver-helperのchromedriverのバージョンを揃える
https://qiita.com/IYD37/items/a5a9eee71dde858d19d3

参考:CircleCIのChromeを最新版に
https://ryotah.hatenablog.com/entry/2017/01/16/214215


OSなど何か前提条件が自分と違うため、上手くいかなかったと思います。
ex.apt-getが使えないなど。



### 補足情報（FW/ツールのバージョンなど）

環境設定やOSについての知識が乏しく、この問題を解決するために必要な情報を判断することができなかったため、
自分がわかる範囲で手がかりになりそうな情報を以下に記載しました。

開発環境　　　　　　　　  　　AWS cloud9
データベース　　　　　　  　　PostgreSQL
Amazon Linux のバージョン　 Amazon Linux AMI release 2018.03 

GemFile
```
source 'https://rubygems.org'
git_source(:github) { |repo| "https://github.com/#{repo}.git" }

ruby '2.5.1'

# Bundle edge Rails instead: gem 'rails', github: 'rails/rails'
gem 'rails', '~> 5.2.1'
# Use postgresql as the database for Active Record
gem 'pg', '>= 0.18', '< 2.0'
# Use Puma as the app server
gem 'puma', '~> 3.11'
# Use SCSS for stylesheets
gem 'sass-rails', '~> 5.0'
# Use Uglifier as compressor for JavaScript assets
gem 'uglifier', '>= 1.3.0'
# See https://github.com/rails/execjs#readme for more supported runtimes
# gem 'mini_racer', platforms: :ruby

# Use CoffeeScript for .coffee assets and views
gem 'coffee-rails', '~> 4.2'
# Turbolinks makes navigating your web application faster. Read more: https://github.com/turbolinks/turbolinks
gem 'turbolinks', '~> 5'
# Build JSON APIs with ease. Read more: https://github.com/rails/jbuilder
gem 'jbuilder', '~> 2.5'
# Use Redis adapter to run Action Cable in production
# gem 'redis', '~> 4.0'
# Use ActiveModel has_secure_password
gem 'bcrypt', '~> 3.1.7'

# Use ActiveStorage variant
# gem 'mini_magick', '~> 4.8'

# Use Capistrano for deployment
# gem 'capistrano-rails', group: :development

# Reduces boot times through caching; required in config/boot.rb
gem 'bootsnap', '>= 1.1.0', require: false

group :development, :test do
  # Call 'byebug' anywhere in the code to stop execution and get a debugger console
  gem 'byebug', platforms: [:mri, :mingw, :x64_mingw]
  gem 'factory_bot_rails', '~> 4.11'
end

group :development do
  # Access an interactive console on exception pages or by calling 'console' anywhere in the code.
  gem 'web-console', '>= 3.3.0'
  gem 'listen', '>= 3.0.5', '< 3.2'
  # Spring speeds up development by keeping your application running in the background. Read more: https://github.com/rails/spring
  gem 'spring'
  gem 'spring-watcher-listen', '~> 2.0.0'
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

# Windows does not include zoneinfo files, so bundle the tzinfo-data gem
gem 'tzinfo-data', platforms: [:mingw, :mswin, :x64_mingw, :jruby]
gem 'slim-rails'
gem 'html2slim'
gem 'bootstrap'
gem 'rails_autolink'
```

教材と違う環境で進めているため、そもそも間違った環境を作ってしまっているのかもしれません。
また、ひとつ気がかりなのは、教材で出てきた「windowsであればUbuntuをインストールする」というところを飛ばした点です。
awsで勉強を進めていくのには関係がないんじゃないかなと考えたため、飛ばしましたが正しい判断だったのでしょうか...

その他解決に必要な情報があれば、教えていただけると幸いです。
まとまっていない質問になりましたが、どうぞよろしくお願いします。

最後まで読んでくださりありがとうございます。
お力添えよろしくお願いします。






###　変更後



連絡お待たせしました。
ご助言通りに試した後、
Rspecを実行したところ、以下のエラーが起きました。




``` 

$  bundle exec rspec spec/system/tasks_spec.rb

Capybara starting Puma...
* Version 3.12.0 , codename: Llamas in Pajamas
* Min threads: 0, max threads: 4
* Listening on tcp://127.0.0.1:33295
/home/ec2-user/.rvm/gems/ruby-2.5.1/bin/rspec: No such file or directory - google-chrome
/home/ec2-user/.rvm/gems/ruby-2.5.1/bin/rspec: No such file or directory - google-chrome
F

Failures:

  1) タスク管理機能 一覧表示機能 ユーザーAがログインしているとき ユーザーAが作成したタスクが表示される
     Got 0 failures and 2 other errors:

     1.1) Failure/Error: visit login_path
          
          NoMethodError:
            undefined method `chomp' for nil:NilClass
          
          
          
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/webdrivers-3.7.0/lib/webdrivers/chromedriver.rb:69:in `chrome_version'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/webdrivers-3.7.0/lib/webdrivers/chromedriver.rb:55:in `release_version'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/webdrivers-3.7.0/lib/webdrivers/chromedriver.rb:19:in `latest_version'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/webdrivers-3.7.0/lib/webdrivers/common.rb:37:in `desired_version'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/webdrivers-3.7.0/lib/webdrivers/common.rb:16:in `update'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/webdrivers-3.7.0/lib/webdrivers/selenium.rb:7:in `driver_path'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/selenium-webdriver-3.14.0/lib/selenium/webdriver/chrome/driver.rb:38:in `initialize'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/selenium-webdriver-3.14.0/lib/selenium/webdriver/common/driver.rb:44:in `new'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/selenium-webdriver-3.14.0/lib/selenium/webdriver/common/driver.rb:44:in `for'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/selenium-webdriver-3.14.0/lib/selenium/webdriver.rb:86:in `for'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/capybara-3.6.0/lib/capybara/selenium/driver.rb:31:in `browser'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/capybara-3.6.0/lib/capybara/selenium/driver.rb:58:in `visit'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/capybara-3.6.0/lib/capybara/session.rb:269:in `visit'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/capybara-3.6.0/lib/capybara/dsl.rb:51:in `block (2 levels) in <module:DSL>'
          # ./spec/system/tasks_spec.rb:13:in `block (4 levels) in <top (required)>'

     1.2) Failure/Error:
            ver = case platform
                    when 'win'
                      chrome_on_windows
                    when /linux/
                      chrome_on_linux
                    when 'mac'
                      chrome_on_mac
                    else
                      raise NotImplementedError, 'Your OS is not supported by webdrivers gem.'
                  end.chomp
          
          NoMethodError:
            undefined method `chomp' for nil:NilClass
          
          
          
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/webdrivers-3.7.0/lib/webdrivers/chromedriver.rb:69:in `chrome_version'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/webdrivers-3.7.0/lib/webdrivers/chromedriver.rb:55:in `release_version'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/webdrivers-3.7.0/lib/webdrivers/chromedriver.rb:19:in `latest_version'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/webdrivers-3.7.0/lib/webdrivers/common.rb:37:in `desired_version'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/webdrivers-3.7.0/lib/webdrivers/common.rb:16:in `update'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/webdrivers-3.7.0/lib/webdrivers/selenium.rb:7:in `driver_path'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/selenium-webdriver-3.14.0/lib/selenium/webdriver/chrome/driver.rb:38:in `initialize'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/selenium-webdriver-3.14.0/lib/selenium/webdriver/common/driver.rb:44:in `new'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/selenium-webdriver-3.14.0/lib/selenium/webdriver/common/driver.rb:44:in `for'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/selenium-webdriver-3.14.0/lib/selenium/webdriver.rb:86:in `for'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/capybara-3.6.0/lib/capybara/selenium/driver.rb:31:in `browser'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/capybara-3.6.0/lib/capybara/selenium/driver.rb:112:in `save_screenshot'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/capybara-3.6.0/lib/capybara/session.rb:709:in `block in save_screenshot'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/capybara-3.6.0/lib/capybara/session.rb:709:in `tap'
          # /home/ec2-user/.rvm/gems/ruby-2.5.1/gems/capybara-3.6.0/lib/capybara/session.rb:709:in `save_screenshot'

Finished in 0.91785 seconds (files took 1.09 seconds to load)
1 example, 1 failure

Failed examples:

rspec ./spec/system/tasks_spec.rb:19 # タスク管理機能 一覧表示機能 ユーザーAがログインしているとき ユーザーAが作成したタスクが表示 される


``` 




なるべく、自力で解決したいのですが、解決の糸口が見えません。
どこを修正すればよいかご助言いただけますか？

ChromeDriverとChromeのバージョンの調整方法について。

自動テストの作成・実行の習慣がないチームに、それを導入した経験がある方の経験談が知りたいです。

参考：コミットログを書く文化がないチーム [https://teratail.com/questions/12542](https://teratail.com/questions/12542)

追記 (2015-09-25)
最近、読んだ本にこんな文がありました。
[https://kindle.amazon.co.jp/post/mpWzXQrCS9WpA-HTl2cIcw](https://kindle.amazon.co.jp/post/mpWzXQrCS9WpA-HTl2cIcw)
> ... テストは病みつきになるという私の主張にみなさんが同意しないかもしれない唯一の理由は、みなさんが試してみたことがないということです。...

学校や研修で、テストを書いてグリーン状態を保ちながら改善、拡張をしていくという経験をした人が増える(増やす)ことが大事なのかもしれません。
(シノゴノいうより経験しさえすれば...)

追記 (2015-11-07)
・11/31  時点で  評価点数が一番多かった回答をベストアンサーにしようと思います。

追記 (2015-10-04)
・teratail サイトでは機能追加、変更の際にどんなテストを実施しているのかを知りたいです。 

追記 (2015-09-17)
*  github のサービスで テストのコードカバレッジレポートを作ってくれるものがあります。(coverails)
レポート例： [https://coveralls.io/builds/867027/source?filename=lib%2Fboard.rb](https://coveralls.io/builds/867027/source?filename=lib%2Fboard.rb)

学校や新人研修でのプログラミングの課題の評価は,
   テスト・カバレッジを含めることが当たり前
のことになればと思っています。

自動テストを書く習慣がないチーム

ruby on rails 5.2

### 実現したいこと
FactoryBotで関連付けを正しく設定したい

### 発生している問題・エラーメッセージ
```ここに言語を入力
# /usr/local/bundle/gems/factory_bot-6.0.2/lib/factory_bot/attribute_assigner.rb:16:in `block (2 levels) in object'
     # /usr/local/bundle/gems/factory_bot-6.0.2/lib/factory_bot/attribute_assigner.rb:15:in `each'
     # /usr/local/bundle/gems/factory_bot-6.0.2/lib/factory_bot/attribute_assigner.rb:15:in `block in object'
     # /usr/local/bundle/gems/factory_bot-6.0.2/lib/factory_bot/attribute_assigner.rb:14:in `tap'
     # /usr/local/bundle/gems/factory_bot-6.0.2/lib/factory_bot/attribute_assigner.rb:14:in `object'
     # /usr/local/bundle/gems/factory_bot-6.0.2/lib/factory_bot/evaluation.rb:13:in `object'
     # /usr/local/bundle/gems/factory_bot-6.0.2/lib/factory_bot/strategy/create.rb:9:in `result'
     # /usr/local/bundle/gems/factory_bot-6.0.2/lib/factory_bot/factory.rb:43:in `run'
     # /usr/local/bundle/gems/factory_bot-6.0.2/lib/factory_bot/factory_runner.rb:29:in `block in run'
     # /usr/local/bundle/gems/activesupport-5.2.5/lib/active_support/notifications.rb:170:in `instrument'
     # /usr/local/bundle/gems/factory_bot-6.0.2/lib/factory_bot/factory_runner.rb:28:in `run'
     # /usr/local/bundle/gems/factory_bot-6.0.2/lib/factory_bot/strategy_syntax_method_registrar.rb:28:in `block in define_singular_strategy_method'
     # ./spec/requests/apis/v2/hoge.rb:5:in `block (3 levels) in <top (required)>'

Finished in 0.62091 seconds (files took 15.52 seconds to load)
1 example, 1 failure

Failed examples:

rspec ./spec/requests/apis/v2/hoge.rb:15 # hogehoge piyopiyo 

```
1対多のモデルをFactoryBotで実装してるところです。

[FactoryBotでbelongs_toとhas_manyの関係にあるやつ](https://qiita.com/roba4coding/items/849ff18c4f57d3c4aff8)
上記を参考に無限ループにならないようしたつもりですが、エラーとなります。
※エラーメッセージは大量のせいか？青字だけで肝心の赤字が見えない状態。


### 該当のソースコード

## rspec
※コメントアウトを外すとエラーになる
/spec/factories/smart_lock_providers.rb
```ruby

FactoryBot.define do
  factory :smart_lock_provider do
    smart_lock_organizations{
      [FactoryBot.build(:smart_lock_organization, smart_lock_provider: nil)]
    }
    # ↓が問題の部分
    # smart_lock_doors{
    #   [FactoryBot.build(:smart_lock_door, smart_lock_provider: nil)]
    # }
  end
end
```

/spec/factories/smart_lock_organizations.rb
```ruby
FactoryBot.define do
  factory :smart_lock_organization do
    smart_lock_provider
    key { 'key' }
    name { 'name' }
  end
end
```

/spec/factories/smart_lock_doors.rb
```ruby
FactoryBot.define do
  factory :smart_lock_door do
    smart_lock_provider
    smart_lock_organization
    key { 'xxxxxx' }
    name { 'xxxxxx' }
  end
end
```

これを実行するとエラーになる
/spec/requests/apis/v2/hoge.rb
```ruby
require 'rails_helper'

RSpec.describe 'hogehoge', type: :request do
  describe "piyopiyo" do
    let!(:smart_lock_door) { create(:smart_lock_door) }
    it do
       expect(1 + 2).to eq 3
    end
  end
end

```

## model

```ruby
class SmartLockProvider < ActiveRecord::Base
  has_many :smart_lock_organizations
  has_many :smart_lock_doors
end

```

```ruby
class SmartLockOrganization < ActiveRecord::Base
  belongs_to :smart_lock_provider
  has_many :smart_lock_doors
end
```

```ruby
class SmartLockDoor < ActiveRecord::Base  
  belongs_to :smart_lock_provider, optional: true
  belongs_to :smart_lock_organization, optional: true
end
```

### 試したこと
/spec/factories/smart_lock_providers.rbのコメントアウト部分を外すと、
letにおいて、親から作っても、子から作ってもエラーになる事を確認。


```ruby
 let!(:smart_lock_provider) { create(:smart_lock_provider) }
```
```ruby
 let!(:smart_lock_organization) { create(:smart_lock_organization) }
```
```ruby
 let!(:smart_lock_door) { create(:smart_lock_door) }
```

逆にコメントアウトすると以下の場合でもエラーは出ない事を確認。

つまりコメントアウト部分の記述が問題だとはわかりましたが、どこが悪いか分からずにいます。



FactoryBotの関連付けでエラーになる

rails tutorialを参考にログイン機能やbefore_actionにてログイン済みのみができるアクションを実装しました。
そのテストコードにおいてログインの有無の２パターンでテストを実行したいと思います。

ログインをしていない場合は、単純に制限のあるURLをgetすれば再現できると考えています。
ログインしている場合は、postリクエスト及び必要情報を渡すことでログインを再現できるのではないかと思います。
このことから、下記の通りにテストコードを記述して見ました。が、rspecのログを確認するとログインできていない動作になっております。



 helperにてログイン状態を再現するメソッドを定義

```testhelper
include ApplicationHelper

module TestHelper
  def log_in_as(user, remember_me: '1')
    post login_path, params: { session: {
      email: user.email,
      password: user.password,
      remember_me: remember_me
    } }
  end
end
```
テストヘルパーを全てのスペックで使用できるようにinclude済み

```railshelper
RSpec.configure do |config|
  config.include TestHelper
end
```

```factorybot
FactoryBot.define do
  factory :user, class: :user do
    name { Faker::Name.name }
    sequence(:email) { |n| "example#{n}@example.com" }
    image { Rack::Test::UploadedFile.new(File.join(Rails.root, 'spec/fixtures/test.jpg')) }

    password { 'foobar' }
    password_confirmation { 'foobar' }

    trait :admin do
      admin { true }
    end
  end
end
```

```UsersRequestSpec
describe 'GET #index' do
    subject { response }
    # ユーザーのログインの有無を確認
    describe 'before_action :logged_in_user' do
      let!(:user) { FactoryBot.create(:user) }
      # ユーザーがログインしている場合
      context 'The user is logged in' do
        before do
          log_in_as(user)　←　ログイン状態を再現しているはず
          get users_path
        end
        it 'responds successfully' do
          is_expected.to be_successful
        end

        it 'returns a 200 response' do
          is_expected.to have_http_status(200)
        end
      end
  end
```
![rspecのログ](728e54700e475af90f7280548f918a9c.png)
赤線部分が疑問な箇所になりまして、一本目ではpostした情報を元にuserをログインし、2本目でusers/1(user.id)にアクセスしているのでここまでは期待した動作になっています。しかし、その後にredirectで/loginにアクセスしています。

usercontrollerを下記の通りに示します。（抜粋）
```UserController
before_action :logged_in_user, only: %i[index edit update destroy]

  PER = 10

  def index
    @users = User.page(params[:page]).per(PER)
  end

private
 # ログイン済みユーザーかどうか確認
  def logged_in_user
    # ログインしていないのなら
    unless logged_in?　（解説：sessionにuser.idがあればtureを返す。userがログインしたらuser.idを元にsessionに情報が格納される)
      store_location
      flash[:danger] = 'Please log in.'
      redirect_to login_url
    end
  end
```
rsepcのログをみる限りログインできていないことから、before_actionの logged_in_userによってlogin_urlに飛ばされているのだと思います。

どのようにすればこれのテストを再現することができるのでしょうか？
ちなみに、ブラウザ情では期待している動作になっておりますので、問題はないかと思います。

どんな些細なことでも構いませんので、どなたか教えていただければとても助かります。
よろしくお願いします。

neko_daisukiさんの回答より
test_helperを下記のメソッドを追記
```testhelper
def sign_in(user)
    allow_any_instance_of(ActionDispatch::Request).to receive(:session).and_return(user_id: user.id)
  end
```

```usersrequestspec
subject { response }
      let(:user) { FactoryBot.create(:user) }
      # ユーザーがログインしている場合
      context 'The user is logged in' do
        before do
          sign_in(user) ←　修正
          get edit_user_path(user)
        end
        it 'responds successfully' do
          is_expected.to be_successful
        end

        it 'returns a 200 response' do
          is_expected.to have_http_status(200)
        end
      end
```
rspecを実行した結果
![テスト成功状況](74e158476e63874f5b67a62437a13858.png)
しっかりsessionの値を取得しrenderしていることが確認できます。

neko_daisukiさんの記述していただいたコードでは以前と同じログになったため、下記qiitaの記事を参考にしたところ、成功いたしました。
[request spec で session 値を設定する](https://qiita.com/blueberrystream/items/884d0d23caf50b6553a0)

詳しい挙動等についてはこれから調べるため説明することはできませんが、とりあえず動作することができましたので、同じようにつまづいている方の参考になればと思います。

rspecでログイン状態（session値の設定）を再現する方法について

### 実現したいこと


- [ ]Docker環境にてシステムスペックを動かしたい

### 前提

Docker環境のRails6にてシステムスペックを動かしたいです。

### 発生している問題・エラーメッセージ

```
  Selenium::WebDriver::Error::WebDriverError:
            unable to connect to /root/.cache/selenium/chromedriver/linux64/114.0.5735.90/chromedriver 127.0.0.1:9515
```
### 該当のソースコード

```Ruby
# spec/support/capybara.rb


require 'capybara/rspec'
require 'selenium/webdriver'
Capybara.register_driver :remote_chrome do |app|
  url = ENV['SELENIUM_DRIVER_URL']
  options = ::Selenium::WebDriver::Chrome::Options.new
  options.add_argument('--no-sandbox')
  options.add_argument('--disable-dev-shm-usage')
  # options.add_argument('--headless')
  options.add_argument('--disable-gpu')
  options.add_argument('--window-size=1680,1050')
  Capybara::Selenium::Driver.new(app, browser: :remote, url: url, options: options)
end
RSpec.configure do |config|
  config.before(:each, type: :system, js: true) do
    Capybara.server_host = "0.0.0.0"
    Capybara.app_host = 'http://app'
    driven_by :remote_chrome
  end
end
```

```
# spec/rails_helper.rb

require 'spec_helper'
ENV['RAILS_ENV'] ||= 'test'
require_relative '../config/environment'
# Prevent database truncation if the environment is production
abort("The Rails environment is running in production mode!") if Rails.env.production?
require 'rspec/rails'
require 'factory_bot_rails'

Dir[Rails.root.join("spec/support/**/*.rb")].each { |f| require f }
# 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')].sort.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
  abort e.to_s.strip
end
RSpec.configure do |config|
  # Remove this line if you're not using ActiveRecord or ActiveRecord fixtures
  config.fixture_path = "#{Rails.root}/spec/fixtures"
  config.include FactoryBot::Syntax::Methods
  # 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

  # You can uncomment this line to turn off ActiveRecord support entirely.
  # config.use_active_record = false

  # 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://rspec.info/features/6-0/rspec-rails
  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")
  config.include Rails.application.routes.url_helpers
  config.include FactoryBot::Syntax::Methods
  # config.include CapybaraSpecHelper, type: :system
  # config.include LoginMacros
end

```

```
# spec/spec_helper.rb


# See https://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.
  #   # 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:
  #   # https://rspec.info/features/3-12/rspec-core/configuration/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

```

```
# docker-compose.yml


version: '3'

services:
  db:
    platform: linux/x86_64
    image: mysql:5.7
    command: mysqld --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
    ports:
      - "3306:3306"
    volumes:
      - ./tmp/db:/var/lib/mysql
      - ./my.cnf:/etc/mysql/conf.d/my.cnf
    environment:
      MYSQL_ROOT_PASSWORD: password
      MYSQL_DATABASE: majan_circle_development
  app:
    build:
      context: .
      dockerfile: "./docker/rails/DockerFile"
    command: /bin/sh -c "rm -f tmp/pids/server.pid && bundle exec rails s -p 3000 -b '0.0.0.0'"
    ports:
      - "3000:3000"
    volumes:
      - .:/majan_circle
    depends_on:
      - db
    stdin_open: true
    tty: true
    environment:
      - "SELENIUM_DRIVER_URL=http://selenium_chrome:4444/wd/hub"
  selenium_chrome:
    image: seleniarm/standalone-chromium
    ports:
      - "4444:4444"
    logging:
      driver: none
```


### 試したこと

自分のChromeのバージョンが`114.0.5735.133`なので、`pip install chromedriver-binary==114.0.5735.90.0`のコマンドでバージョンを合わせるようにした

## 追記
ただDocker環境にてwebdriverのイメージを取得したときは自動的にchromeとwebdriverのバージョンが合った状態で
インストールされるとありました（下記記事を参照)
docker-composeファイルの記述が間違っているのでしょうか。
https://qiita.com/Chanmoro/items/9a3c86bb465c1cce738a

うまくいかず手詰まりの状態です。ご教示いただければ幸いです。


Docker環境にてシステムスペックを動かしたい

### 前提・実現したいこと
Rspec,factory_bot_rails,capybaraを使用し、syetemspecのログインテストを再現したいです。

capybaraのドライバはselenium_chrome_headlessに設定しています。




### 発生している問題・エラーメッセージ
bundle exec rspec spec/system/user_spec.rbを実行すると以下のエラーが出る。

```terminal
An error occurred while loading spec_helper.
Failure/Error: reqiure 'capybara/rspec'

NoMethodError:
  undefined method `reqiure' for main:Object
  Did you mean?  require
# ./spec/spec_helper.rb:18:in `<top (required)>'
No examples found.


Finished in 0.00003 seconds (files took 0.14022 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples
```

### 該当のソースコード

```Gemfile
source 'https://rubygems.org'
git_source(:github) { |repo| "https://github.com/#{repo}.git" }

ruby '2.6.3'

# Bundle edge Rails instead: gem 'rails', github: 'rails/rails', branch: 'main'
gem 'rails', '~> 6.1.3'
#Bootstrap
gem 'bootstrap', '~> 4.3.1'
gem 'jquery-rails'
#日本語エラー
gem 'rails-i18n'
# Use sqlite3 as the database for Active Record
gem 'sqlite3', group: [:development, :test]
gem 'pg', group: :production
# Use Puma as the app server
gem 'puma', '~> 5.0'
# Use SCSS for stylesheets
gem 'sass-rails', '>= 6'
# Transpile app-like JavaScript. Read more: https://github.com/rails/webpacker
gem 'webpacker', '~> 5.0'
# Turbolinks makes navigating your web application faster. Read more: https://github.com/turbolinks/turbolinks
gem 'turbolinks', '~> 5'
# Build JSON APIs with ease. Read more: https://github.com/rails/jbuilder
gem 'jbuilder', '~> 2.7'
# Use Redis adapter to run Action Cable in production
# gem 'redis', '~> 4.0'
# Use Active Model has_secure_password
gem 'bcrypt', '~> 3.1.7'

# Use Active Storage variant
# gem 'image_processing', '~> 1.2'

# Reduces boot times through caching; required in config/boot.rb
gem 'bootsnap', '>= 1.4.4', require: false


#CarrierWave導入
gem 'carrierwave'
gem 'fog-aws'
gem 'mini_magick'

#開発環境とテスト環境
group :development, :test do
  # Call 'byebug' anywhere in the code to stop execution and get a debugger console
  gem 'byebug', platforms: [:mri, :mingw, :x64_mingw]
  gem 'rspec-rails', '~> 5.0.0'
  gem 'factory_bot_rails'
  gem 'capybara', '>= 3.26'
  gem 'selenium-webdriver'
end

group :development do
  # Access an interactive console on exception pages or by calling 'console' anywhere in the code.
  gem 'web-console', '>= 4.1.0'
  # Display performance information such as SQL time and flame graphs for each request in your browser.
  # Can be configured to work on production as well see: https://github.com/MiniProfiler/rack-mini-profiler/blob/master/README.md
  gem 'rack-mini-profiler', '~> 2.0'
  gem 'listen', '~> 3.3'
  # Spring speeds up development by keeping your application running in the background. Read more: https://github.com/rails/spring
  gem 'spring'
end

group :test do
  # Adds support for Capybara system testing and selenium driver
 
  # Easy installation and use of web drivers to run system tests with browsers
  gem 'webdrivers'

end

# Windows does not include zoneinfo files, so bundle the tzinfo-data gem
gem 'tzinfo-data', platforms: [:mingw, :mswin, :x64_mingw, :jruby]

```
spec/spec_helper.rb
```
# This file was generated by the `rails generate rspec:install` command. Conventionally, all
# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.
# The generated `.rspec` file contains `--require spec_helper` which will cause
# this file to always be loaded, without a need to explicitly require it in any
# files.
#
# Given that it is always loaded, you are encouraged to keep this file as
# light-weight as possible. Requiring heavyweight dependencies from this file
# will add to the boot time of your test suite on EVERY test run, even for an
# individual file that may not need all of that loaded. Instead, consider making
# a separate helper file that requires the additional dependencies and performs
# the additional setup, and require it from the spec files that actually need
# it.
#
# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration

#Rspecでcapybaraを扱うための読み込み
reqiure 'capybara/rspec'

RSpec.configure do |config|
  #Systemspecを実行するドライバの設定
  config.before(:each, type: :system) do
    driven_by :selenium_chrome_headless
  end
  # 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
```
spec/system/user_spec.rb
```
require 'rails_helper'

describe 'ログイン成功テスト',type: :system do
    describe'user詳細画面が表示される' do
        #仮ユーザー作成
        before do
            user_a =FactoryBot.create(:user,name:'ユーザーA',email:'a@example.com')
        end
        context 'ログインしている時の操作' do
            before do
                #入力された値
                visit: login_path
                fill_in: 'メールアドレス',with: 'a@example.com'
                fill_in: 'パスワード',with: 'password'
                click_botton: 'ログイン'
            end
            it '正しい値が設定してあればログインは成功する' do
                expect(@user.valid?).to eq(true)
            end   
        end
    end
end
```
spec/factories/user.rb
```
FactoryBot.define do
    factroy :user do
        name('テストユーザー')
        email('test@example.com')
        password('password')
    end
end
```
### 試したこと

capybaraの読み込みがうまくいっていないのかと思い
```
RSpec.configure do |config|
  #Systemspecを実行するドライバの設定
  config.before(:each, type: :system) do
     config.include Capybara::DSL ←追記
    driven_by :selenium_chrome_headless
  end
```
DSLで強制読み込みしようと試みましたが、エラー内容が変わりませんでした。

### 補足情報（FW/ツールのバージョンなど）

MacOS 10.15.7

Rspecをまだ触りたてで不足部分が多々あると思いますが、ご教授のほどよろしくお願いします。

Rspec実行時にエラー　An error occurred while loading spec_helper.

### 前提・実現したいこと

Railsの初学者です。RSpecテストを以下の文献を参考に取り組んでいます。
「Everyday Rails RSpecによるRailsテスト入門」 Aaron Summer著　

初期段階としてRSpecやFactoryBotのセットアップの確認をするため、ファクトリーの動作テストを行ったところ、NameError: uninitialized constantエラーが出てきており、躓いているため質問させていただきます。ご教授いただけると幸いです。

### 発生している問題・エラーメッセージ

```
# bin/rspec spec/models/user_spec.rb
Running via Spring preloader in process 134
F

Failures:

  1) User has a valid factory
     Failure/Error: expect(FactoryBot.build(:user)).to be_valid
     
     NameError:
       uninitialized constant User
     # ./spec/models/user_spec.rb:5:in `block (2 levels) in <main>'
     # -e:1:in `<main>'

Finished in 0.08281 seconds (files took 1.82 seconds to load)
1 example, 1 failure

Failed examples:

rspec ./spec/models/user_spec.rb:4 # User has a valid factory
```

### 該当のソースコード
`spec/models/user_spec.rb`
```
require 'rails_helper'

RSpec.describe 'User', type: :model do
  it"has a valid factory"do
    expect(FactoryBot.build(:user)).to be_valid
  end
end
```
`spec/factories/users.rb`
```
FactoryBot.define do
  factory :user do
   first_name {"Aaron"}
   last_name {"Summer"}
  end
end
```
`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!
require 'capybara/rspec'

Dir[Rails.root.join('spec', 'support', '**', '*.rb')].sort.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

  # You can uncomment this line to turn off ActiveRecord support entirely.
  # config.use_active_record = false

  # 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/spec_helper.rb`
```
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
```
### 追記
`config/application.rb`
```
    config.time_zone = 'Tokyo'
    config.generators.test_framework = :rspec
    config.generators.system_tests   = false
    config.generators.stylesheets    = false
    config.generators.javascripts    = false
    config.generators.helper         = false

    config.generators do |g|
      g.test_framework :rspec,
        controller_specs: true,
        model_specs: true,
        request_spec: true,
        view_specs: false,
        helper_specs: false,
        routing_specs: false
    end
```
`Gemfile`
```
gem 'rails', '~> 6.1'
gem 'bootsnap', require: false
gem 'mysql2', '~> 0.5.3'
gem 'puma', '~> 5.2.2'
gem 'sass-rails', '~> 6.0'
gem 'uglifier', '>= 4.2.0'

gem 'jbuilder', '~> 2.11'

gem 'solidus', '~> 2.11.0'
gem 'solidus_auth_devise'
gem 'solidus_i18n', github: 'solidusio-contrib/solidus_i18n', branch: 'master'
gem 'paypalhttp', '~> 1.0'
gem 'solidus_auth_devise'
gem 'solidus_paypal_commerce_platform'

group :development, :test do
  gem 'byebug', platforms: [:mri, :mingw, :x64_mingw]
  gem 'rspec-rails'
  gem 'factory_bot_rails'
  gem 'pry-rails'
  gem 'pry-doc'
  gem 'pry-byebug'
  gem 'rails-erd'
  gem 'annotate'
  gem 'rubocop-airbnb'
  gem 'spring-commands-rspec'
end

group :test do
  gem 'capybara'
  gem 'webdrivers'
  gem 'launchy'
end

group :development do
  gem 'web-console', '>= 4.1.0'
  gem 'listen', '>= 3.0.5', '< 4.0'
  gem 'spring'
  gem 'spring-watcher-listen', '~> 2.0.1'
end

gem "aws-sdk", "~> 3.0"
gem "aws-sdk-s3", require: false
gem 'ast', '~> 2.4', '>= 2.4.2'
```
### 試したこと

「uninitialized constant」というエラーから、ファクトリーが定義されてない？FactoryBotに原因があるのではと考え、様々な記事や質問を調べ作り直したりRspec・FactoryBotの設定を見直してみましたが、エラーは変わりませんでした。

### 補足情報（FW/ツールのバージョンなど）
Rails 6.1.3.2
ruby 2.7.3
RSpec 3.10
factory_bot 6.2.0

RSpec テスト実行時のNameError: uninitialized constant FactoryBotのエラーについて

RSpec、とりわけリクエストスペックでの質問です。
リクエストスペックで!session[:user_id].nil?がなぜ使えるのかが疑問です。

session[:user_id] = user.idを行った際はsessionメソッドは使えません。とエラーが出ました。

```
# spec/support/login_support.rb

module LoginUser

  # このメソッドがなぜリクエストスペックで使えるのかが疑問
  def is_logged_in?
    !session[:user_id].nil?
  end

  # これは使えない
  def test_log_in(user)
      session[:user_id] = user.id
  end

  RSpec.configure do |config|
    config.include LoginUser
  end
end
```

```
# spec/request/sessions_request_spec.rb

require 'rails_helper'

RSpec.describe "Sessions", type: :request do
  let(:user) { FactoryBot.attributes_for(:user) }

  describe "destroy" do
    before do
      post users_path, params: { user: user }
    end
    
    # このitは通る
    it "ログイン状態じゃなくなる" do
       delete logout_path(user)
       expect(is_logged_in?).to_not be_truthy    # このexpectで使用
    end
  end

  describe "create" do
　　　　# このitはエラー
      it "sessionメソッドを使いログイン", focus: true do
        test_log_in( FactoryBot.create(:user) )  # test_log_inはここで使用
        expect(is_logged_in?).to be_truthy
      end
   end
end
```

```
# エラー文

Failure/Error: session[:user_id] = user.id
     
     NoMethodError:
       undefined method `session' for nil:NilClass
```


system specでsessionメソッドが使えないのは知っていましたが、リクエストスペックでも使えないのでしょうか?

繰り返しになりますが、その場合なぜis_logged_inメソッドは使えたのでしょうか？

よろしくお願い致します。