#<RSpec::ExampleGroups::UserName:> 的未定义方法“构建”

Question

我目前正在开发 Rails 4.2.6 和 RSpec 3.7 版本。当我运行我的测试出现以下错误：

undefined method `build' for #<RSpec::ExampleGroups::UserName:0x007ff984a99d38>

触发此错误的是以下代码。需要 'rails_helper'

RSpec.describe User, "name" do
  #setup
  it "returns the email" do
    #build
    user = build(:user, email: "everlastingwardrobe@example.com")
    # excercise and verify
    expect(user.email).to eq "everlastingwardrobe@example.com"
  end
end

我正在使用构建而不是创建，因为我不想将数据持久保存到数据库中。但是我正在使用 factory_bot_rails 所以我应该可以访问这个方法。

这是我的 Gemfile：

group :development, :test do
  gem 'rspec'
  gem 'rspec-rails'
  gem 'factory_bot_rails'
  gem 'byebug'
  gem 'pry'
  gem 'pry-nav'
  gem 'pry-stack_explorer'
end

group :test do
  gem "capybara"
  gem "selenium-webdriver"
end

spec_helper.rb

# This file is copied to spec/ when you run 'rails generate rspec:install'
ENV['RAILS_ENV'] ||= 'test'
require File.expand_path('../../config/environment', __FILE__)

require 'spec_helper'
require "rspec/rails"
require "capybara/rspec"


# Prevent database truncation if the environment is production
abort("The Rails environment is running in production mode!") if Rails.env.production?

# 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 this line.
ActiveRecord::Migration.maintain_test_schema!

Capybara.register_driver :selenium_chrome do |app|
 Capybara::Selenium::Driver.new(app, browser: :chrome)
end

Capybara.javascript_driver = :selenium_chrome

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
  #
  # # This block must be here, do not combine with the other `before(:each)` block.
  # # This makes it so Capybara can see the database.
  # config.before(:each) do
  #   DatabaseCleaner.start
  # end
  #
  # config.after(:each) do
  #   DatabaseCleaner.clean
  # end
end

我该如何解决这个问题，或者我应该改用 create？

Answer 1

build 方法是 FactoryGirl 或 FactoryBot 命名空间的一部分

你为什么不试试

FactoryBot.build(:user :email => 'everlastingwardrobe@example.com')

Answer 2

添加后gem

在 spec/support/factory_bot.rb
添加到factory_bot.rb

RSpec.configure do |config| config.include FactoryBot::Syntax::Methods end
添加 rails_helper.rb require 'support/factory_bot'

#<RSpec::ExampleGroups::UserName:> 的未定义方法“构建”

undefined method `build' for #<RSpec::ExampleGroups::UserName:>

rspec

ruby-on-rails-4

factory-bot