从rspec 2开始，你可以使用以下代码:

# in spec/spec_helper.rb
RSpec.configure do |config|
  config.filter_run :focus => true
  config.run_all_when_everything_filtered = true
end

# in spec/any_spec.rb
describe "something" do
  it "does something", :focus => true do
    # ....
  end
end

您可以将一个正则表达式传递给spec命令，该命令将只运行与您提供的名称匹配的块。

spec path/to/my_spec.rb -e "should be the correct answer"

2019更新:Rspec2从'spec'命令切换到'rspec'命令。

从项目的根目录运行命令:

# run all specs in the project's spec folder
bundle exec rspec 

# run specs nested under a directory, like controllers
bundle exec rspec spec/controllers

# run a single test file
bundle exec rspec spec/controllers/groups_controller_spec.rb

# run a test or subset of tests within a file
# e.g., if the 'it', 'describe', or 'context' block you wish to test
# starts at line 45, run:
bundle exec rspec spec/controllers/groups_controller_spec.rb:45

此外，您可以使用——example (-e)选项来运行特定的测试，这些测试部分或完全匹配给定测试路径的'it'、'describe'或'context'块中的文本标签:

# run groups controller specs in blocks with a label containing 'spaghetti flag is false'
bundle exec rspec spec/controllers/groups_controller_spec.rb -e 'spaghetti flag is false'

# Less granularly, you can run specs for blocks containing a substring of text 
# that matches one or more block labels, like 'spaghetti' or 'paghett'
bundle exec rspec spec/controllers/groups_controller_spec.rb -e spaghetti

这将运行块内嵌套的所有测试，标签与示例选项接收到的字符串参数匹配。

When using the example option, I recommend also appending --format documentation (shorthand: -f documentation) to your bundle command (e.g., bundle exec rspec spec/some_file.rb -e spaghetti -f documentation). Documentation-formatting replaces the normal ./F output with an easy-to-read pretty printed breakdown showing the nested block labels for the examples you're running and outputs the printed label for each example (it block) in green or red to denote whether it passed or failed. This provides better confirmation that your example argument matches the specs you intended to run, and it gives live visibility to which examples are passing/failing during longer test runs where the example argument matches many block labels and/or matched blocks contain many nested examples.

附加阅读(文档链接)

例子的选择 格式选项

通常我会这样做:

rspec ./spec/controllers/groups_controller_spec.rb:42

其中42表示我要运行的测试行。

你也可以使用标签。在这里看到的。

使用bundle exec:

bundle exec rspec ./spec/controllers/groups_controller_spec.rb:42

假设你在一个rspec 2的rails 3项目中，从rails根目录:

  bundle exec rspec spec/controllers/groups_controller_spec.rb 

应该没问题。我厌倦了输入，所以我创建了一个别名来缩短'bundle exec rspec'到'bersp'

'bundle exec'可以加载gem文件中指定的gem环境:http://gembundler.com/

Rspec2从'spec'命令切换到'rspec'命令。

@ apne潜水的答案是一个整洁的解决这个问题的方法。然而，现在我们在Rspec 3.3中有了一个新方法。我们可以简单地运行rspec spec/unit/baseball_spec。Rb [#context:#it]而不是行号。从这里开始:

RSpec 3.3引入了一种识别示例的新方法[…] 例如，以下命令: $ rspec spec/unit/baseball_spec.rb[1:2,1:4] …将运行在spec/unit/baseball_spec.rb中定义的第一个顶级组下定义的第二个和第四个示例或组。

所以与其这样做 rspec规范/单位/ baseball_spec。第42行测试是第一个测试，我们可以简单地做 rspec规范/单位/ baseball_spec。Rb[1:1]或rspec spec/unit/baseball_spec。Rb[1:1:1]取决于测试用例的嵌套程度。