Spec spec を実行後以下のエラーが出ました。

前提・実現したいこと

rails5中級チュートリアルの３章テストの２つ目のテストを書き終えた後です。

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

エラーメッセージ

Failure/Error: let(:user) { create(:user) }
     
     NoMethodError:
       undefined method `name=' for #<User id: nil, email: "", created_at: nil, updated_at: nil>

該当のソースコード

# spec/factories/users.rb
FactoryBot.define do
    factory :user do
      sequence(:name) { |n| "test#{n}" }
      
      sequence(:email) { |n| "test#{n}@test.com" }
      password {'123456'}
      password_confirmation {'123456'}
    end
  end

require "rails_helper"

RSpec.feature "Login", :type => :feature do
    let(:user) { create(:user) }

  scenario 'ユーザーがloginページにリダイレクトされ、ログインに成功する', js: true do
    user
    visit root_path
    find('nav a', text: 'Login').click
    fill_in 'user[email]', with: user.email
    fill_in 'user[password]', with: user.password
    find('.login-button').click
    expect(page).to have_selector('#user-settings')
  end

end

# 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

  require 'capybara/poltergeist'
  require 'factory_bot_rails'
  require 'capybara/rspec'
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 = 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")
  config.before(:suite) do
    DatabaseCleaner.clean_with(:truncation)
  end

  config.before(:each) do
    DatabaseCleaner.strategy = :transaction
  end

  config.before(:each, :js => true) do
    DatabaseCleaner.strategy = :truncation
  end

  config.before(:each) do
    DatabaseCleaner.start
  end

  config.after(:each) do
    DatabaseCleaner.clean
  end

  config.include Devise::Test::IntegrationHelpers, type: :feature
  config.include FactoryBot::Syntax::Methods
  Capybara.javascript_driver = :poltergeist
  Capybara.server = :puma
end

試したこと

FactoryBot.create(:user)に変更しても変わらず
sequence(:name)のname部分をnamにするとエラー文も undefined method `nam=' for に変わったのでこの辺りを変えては戻してを繰り返しても直りませんでした。
５時間ほど調べましたがわからないので登録して初投稿です。
もし分かる方いらっしゃれば、ご教授お願いいたします。

補足情報（FW/ツールのバージョンなど）

ここにより詳細な情報を記載してください。

行動規範の内容に同意します

回答2件

<User id: nil, email: "", created_at: nil, updated_at: nil>
とあります。

モデルUserに　name がないのでは？
migrationを確認してください

投稿2020/02/09 13:16

winterboum

総合スコア23329

kata1130

2020/02/10 01:34

返信ありがとうございます。実行してみたところ違うエラーが出てしまいました。 Failure/Error: visit root_path Capybara::DriverNotFoundError: no driver called :poltergeist was found, available drivers: :rack_test, :selenium, :selenium_headless, :selenium_chrome, :selenium_chrome_headless capybara,chromdriverを最新版にアップデートしましたが直りませんでした。

行動規範の内容に同意します