从RSpec开始 - <top（required）=“”>'：未初始化的常量RSpec（NameError）

Question

我刚开始使用RSpec。我正在关注Code School的课程：http://rspec.codeschool.com/levels/1

我使用Cloud 9保存所有文件并运行Ruby。

这是我的目录结构：

这是zombie.rb的代码：

class Zombie
end

这是zombie_spec.rb的代码：

require "spec_helper"
require "zombie"

这是我的结果：

rspec_example/spec $ ruby zombie_spec.rb 
/usr/local/rvm/rubies/ruby-        2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require':     cannot load such file -- spec_helper (LoadError)
        from /usr/local/rvm/rubies/ruby-    2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
        from zombie_spec.rb:1:in `<main>'

当我尝试更改zombie_spec.rb中的require路径时：

require "./spec_helper"
require "zombie"

我明白了：

    rspec_example/spec $ ruby zombie_spec.rb 
/home/ubuntu/workspace/rspec_example/spec/spec_helper.rb:19:in `<top     (required)>': uninitialized constant RSpec (NameError)
        from /usr/local/rvm/rubies/ruby-    2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
        from /usr/local/rvm/rubies/ruby-    2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
        from zombie_spec.rb:1:in `<main>'

如果我再次将规格更改为：

require "./spec_helper"
require "../zombie"

我明白了：

    rspec_example/spec $ ruby zombie_spec.rb 
/home/ubuntu/workspace/rspec_example/spec/spec_helper.rb:19:in `<top     (required)>': uninitialized constant RSpec (NameError)
        from /usr/local/rvm/rubies/ruby-    2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
        from /usr/local/rvm/rubies/ruby-    2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
        from zombie_spec.rb:1:in `<main>'

这就是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!

  # This setting enables warnings. It's recommended, but in some cases may
  # be too noisy due to issues in dependencies.
  config.warnings = true

  # 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

Answer 1

我明白了：你没有通过ruby运行xxx_spec.rb文件，你通过rspec运行它。我看到那个orde打败了我。

Answer 2

老兄，你想运行RSpec而你正在使用ruby命令 确保你像这样运行RSpec。

rspec  spec/zombie_spec.rb