rspec-core 2.5.1 → 2.6.0

data/features/command_line/tag.feature

@@ -19,7 +19,8 @@ Feature: --tag option
       """
       describe "group with tagged specs" do
         it "example I'm working now", :focus => true do; end
-        it "special example", :type => 'special' do; end
+        it "special example with string", :type => 'special' do; end
+        it "special example with symbol", :type => :special do; end
         it "slow example", :skip => true do; end
         it "ordinary example", :speed => 'slow' do; end
         it "untagged example" do; end
@@ -27,48 +28,63 @@ Feature: --tag option
       """
 
   Scenario: filter examples with non-existent tag
-    When I run "rspec . --tag mytag"
+    When I run `rspec . --tag mytag`
     And the examples should all pass
 
   Scenario: filter examples with a simple tag
-    When I run "rspec . --tag focus"
-    Then the output should contain "Run filtered using {:focus=>true}"
+    When I run `rspec . --tag focus`
+    Then the output should contain "Run filtered including {:focus=>true}"
     And the examples should all pass
 
   Scenario: filter examples with a simple tag and @
-    When I run "rspec . --tag @focus"
-    Then the output should contain "Run filtered using {:focus=>true}"
+    When I run `rspec . --tag @focus`
+    Then the output should contain "Run filtered including {:focus=>true}"
     Then the examples should all pass
 
   Scenario: filter examples with a name:value tag
-    When I run "rspec . --tag type:special"
+    When I run `rspec . --tag type:special`
     Then the output should contain:
       """
-      Run filtered using {:type=>"special"}
+      Run filtered including {:type=>"special"}
       """
+    And the output should contain "2 examples"
     And the examples should all pass
   
   Scenario: filter examples with a name:value tag and @
-    When I run "rspec . --tag @type:special"
+    When I run `rspec . --tag @type:special`
     Then the output should contain:
       """
-      Run filtered using {:type=>"special"}
+      Run filtered including {:type=>"special"}
       """
     And the examples should all pass
   
   Scenario: exclude examples with a simple tag
-    When I run "rspec . --tag ~skip"
+    When I run `rspec . --tag ~skip`
+    Then the output should contain "Run filtered excluding {:skip=>true}"
     Then the examples should all pass
 
   Scenario: exclude examples with a simple tag and @
-    When I run "rspec . --tag ~@skip"
+    When I run `rspec . --tag ~@skip`
+    Then the output should contain "Run filtered excluding {:skip=>true}"
     Then the examples should all pass
     
   Scenario: exclude examples with a name:value tag
-    When I run "rspec . --tag ~speed:slow"
+    When I run `rspec . --tag ~speed:slow`
+    Then the output should contain:
+      """
+      Run filtered excluding {:speed=>"slow"}
+      """
     Then the examples should all pass
   
   Scenario: exclude examples with a name:value tag and @
-    When I run "rspec . --tag ~@speed:slow"
+    When I run `rspec . --tag ~@speed:slow`
+    Then the output should contain:
+      """
+      Run filtered excluding {:speed=>"slow"}
+      """
     Then the examples should all pass
 
+  Scenario: filter examples with a simple tag, exclude examples with another tag
+    When I run `rspec . --tag focus --tag ~skip`
+    Then the output should contain "Run filtered including {:focus=>true}, excluding {:skip=>true}"
+    And the examples should all pass

data/features/configuration/alias_example_to.feature

@@ -0,0 +1,48 @@
+Feature: alias_example_to
+
+  Use `config.alias_example_to` to create new example group methods
+  that define examples with the configured metadata.
+
+  If you set the `treat_symbols_as_metadata_keys_with_true_values` config option
+  to `true`, you can specify metadata using only symbols.
+
+  Scenario: Use alias_example_to to define focused example
+    Given a file named "alias_example_to_spec.rb" with:
+      """
+      RSpec.configure do |c|
+        c.alias_example_to :fit, :focused => true
+        c.filter_run :focused => true
+      end
+
+      describe "an example group" do
+        it "does one thing" do
+        end
+
+        fit "does another thing" do
+        end
+      end
+      """
+    When I run `rspec alias_example_to_spec.rb --format doc`
+    Then the output should contain "does another thing"
+    And the output should not contain "does one thing"
+
+  Scenario: use symbols as metadata
+    Given a file named "use_symbols_as_metadata_spec.rb" with:
+      """
+      RSpec.configure do |c|
+        c.treat_symbols_as_metadata_keys_with_true_values = true
+        c.alias_example_to :fit, :focused
+        c.filter_run :focused
+      end
+
+      describe "an example group" do
+        it "does one thing" do
+        end
+
+        fit "does another thing" do
+        end
+      end
+      """
+    When I run `rspec use_symbols_as_metadata_spec.rb --format doc`
+    Then the output should contain "does another thing"
+    And the output should not contain "does one thing"

data/features/configuration/custom_settings.feature

@@ -29,7 +29,7 @@ Feature: custom settings
         end
       end
       """
-    When I run "rspec ./additional_setting_spec.rb"
+    When I run `rspec ./additional_setting_spec.rb`
     Then the examples should all pass
 
   Scenario: default to true
@@ -55,7 +55,7 @@ Feature: custom settings
         end
       end
       """
-    When I run "rspec ./additional_setting_spec.rb"
+    When I run `rspec ./additional_setting_spec.rb`
     Then the examples should all pass
 
   Scenario: overridden in a subsequent RSpec.configure block
@@ -79,6 +79,6 @@ Feature: custom settings
         end
       end
       """
-    When I run "rspec ./additional_setting_spec.rb"
+    When I run `rspec ./additional_setting_spec.rb`
     Then the examples should all pass
 

data/features/configuration/fail_fast.feature

@@ -21,7 +21,7 @@ Feature: fail fast
         end
       end
       """
-    When I run "rspec spec/example_spec.rb"
+    When I run `rspec spec/example_spec.rb`
     Then the examples should all pass
 
   Scenario: fail_fast with first example failing (only runs the one example)
@@ -37,7 +37,7 @@ Feature: fail fast
         end
       end
       """
-    When I run "rspec spec/example_spec.rb -fd"
+    When I run `rspec spec/example_spec.rb -fd`
     Then the output should contain "1 example, 1 failure"
 
   Scenario: fail_fast with multiple files, second example failing (only runs the first two examples)
@@ -73,5 +73,5 @@ Feature: fail fast
         end
       end
       """
-    When I run "rspec spec"
+    When I run `rspec spec`
     Then the output should contain "2 examples, 1 failure"

data/features/configuration/read_options_from_file.feature

@@ -30,7 +30,7 @@ Feature: read command line configuration options from files
         end
       end
       """
-    When I run "rspec ./spec/example_spec.rb"
+    When I run `rspec ./spec/example_spec.rb`
     Then the examples should all pass
 
   Scenario: custom options file
@@ -47,7 +47,7 @@ Feature: read command line configuration options from files
         end
       end
       """
-    When I run "rspec spec/example_spec.rb --options my.options"
+    When I run `rspec spec/example_spec.rb --options my.options`
     Then the examples should all pass
 
   Scenario: RSpec ignores ./.rspec when custom options file is used
@@ -67,7 +67,7 @@ Feature: read command line configuration options from files
         end
       end
       """
-    When I run "rspec spec/example_spec.rb --options my.options"
+    When I run `rspec spec/example_spec.rb --options my.options`
     Then the examples should all pass
 
   Scenario: using ERB in .rspec
@@ -83,5 +83,5 @@ Feature: read command line configuration options from files
         end
       end
       """
-    When I run "rspec ./spec/example_spec.rb"
+    When I run `rspec ./spec/example_spec.rb`
     Then the examples should all pass

data/features/example_groups/basic_structure.feature

@@ -4,21 +4,17 @@ Feature: basic structure (describe/it)
   behave, organized in groups. It uses the words "describe" and "it" so we can
   express concepts like a conversation:
 
-    "Describe an account when it is first opened."
-    "It has a balance of zero."
+      "Describe an account when it is first opened."
+      "It has a balance of zero."
 
-  The describe() method creates a subclass of RSpec::Core::ExampleGroup. The
-  block passed to describe() is evaluated in the context of that class, so any
-  class methods of ExampleGroup are at your disposal within that block.
-
-  Within a group, you can declare nested groups using the describe() or
-  context() methods. A nested group is actually a subclass of the outer group,
-  so it has access to same methods as the outer group, as well as any class
-  methods defined in the outer group.
-
-  The it() method accepts a block, which is later executed in the context of
-  an instance of the group in which it is declared.
+  The `describe` method creates an example group.  Within the block passed to
+  `describe` you can declare nested groups using the `describe` or `context`
+  methods, or you can declare examples using the `it` or `specify` methods.
 
+  Under the hood, an example group is a class in which the block passed to
+  `describe` or `context` is evaluated. The blocks passed to `it` are evaluated
+  in the context of an _instance_ of that class.
+  
   Scenario: one group, one example
     Given a file named "sample_spec.rb" with:
     """
@@ -27,7 +23,7 @@ Feature: basic structure (describe/it)
       end
     end
     """
-    When I run "rspec sample_spec.rb -fn"
+    When I run `rspec sample_spec.rb -fn`
     Then the output should contain:
       """
       something
@@ -48,7 +44,7 @@ Feature: basic structure (describe/it)
       end
     end
     """
-    When I run "rspec nested_example_groups_spec.rb -fdoc"
+    When I run `rspec nested_example_groups_spec.rb -fdoc`
     Then the output should contain:
       """
       something

data/features/example_groups/shared_context.feature

@@ -0,0 +1,74 @@
+Feature: shared context
+
+  Use `shared_context` to define a block that will be evaluated in the context
+  of example groups either explicitly, using `include_context`, or implicitly by
+  matching metdata.
+
+  Background:
+    Given a file named "shared_stuff.rb" with:
+      """
+      shared_context "shared stuff", :a => :b do
+        before { @some_var = :some_value }
+        def shared_method
+          "it works"
+        end
+        let(:shared_let) { {'arbitrary' => 'object'} }
+        subject do
+          'this is the subject'
+        end
+      end
+      """
+  
+  Scenario: declare shared context and include it with include_context
+    Given a file named "shared_context_example.rb" with:
+      """
+      require "./shared_stuff.rb"
+
+      describe "group that includes a shared context using 'include_context'" do
+        include_context "shared stuff"
+
+        it "has access to methods defined in shared context" do
+          shared_method.should eq("it works")
+        end
+
+        it "has access to methods defined with let in shared context" do
+          shared_let['arbitrary'].should eq('object')
+        end
+
+        it "runs the before hooks defined in the shared context" do
+          @some_var.should be(:some_value)
+        end
+
+        it "accesses the subject defined in the shared context" do
+          subject.should eq('this is the subject')
+        end
+      end
+      """
+    When I run `rspec shared_context_example.rb`
+    Then the examples should all pass
+
+  Scenario: declare shared context and include it with metadata
+    Given a file named "shared_context_example.rb" with:
+      """
+      require "./shared_stuff.rb"
+
+      describe "group that includes a shared context using metadata", :a => :b do
+        it "has access to methods defined in shared context" do
+          shared_method.should eq("it works")
+        end
+
+        it "has access to methods defined with let in shared context" do
+          shared_let['arbitrary'].should eq('object')
+        end
+
+        it "runs the before hooks defined in the shared context" do
+          @some_var.should be(:some_value)
+        end
+
+        it "accesses the subject defined in the shared context" do
+          subject.should eq('this is the subject')
+        end
+      end
+      """
+    When I run `rspec shared_context_example.rb`
+    Then the examples should all pass

data/features/example_groups/shared_example_group.feature

@@ -1,19 +1,23 @@
-Feature: shared example group
+Feature: shared examples
 
-  Shared example groups let you describe behaviour of types or modules. When
+  Shared examples let you describe behaviour of types or modules. When
   declared, a shared group's content is stored. It is only realized in the
   context of another example group, which provides any context the shared group
   needs to run.
 
-  A shared group is included in another group using the it_behaves_like() or
-  it_should_behave_like() methods.
+  A shared group is included in another group using any of:
+  
+      include_examples "name"      # include the examples in the current context
 
-  Scenario: shared example group applied to two groups
+      it_behaves_like "name"       # include the examples in a nested context
+      it_should_behave_like "name" # include the examples in a nested context
+
+  Scenario: shared examples group included in two groups
     Given a file named "collection_spec.rb" with:
     """
     require "set"
 
-    shared_examples_for "a collection" do
+    shared_examples "a collection" do
       let(:collection) { described_class.new([7, 2, 4]) }
 
       context "initialized with 3 items" do
@@ -45,7 +49,7 @@ Feature: shared example group
       it_behaves_like "a collection"
     end
     """
-    When I run "rspec collection_spec.rb --format documentation"
+    When I run `rspec collection_spec.rb --format documentation`
     Then the examples should all pass
     And the output should contain:
       """
@@ -75,7 +79,7 @@ Feature: shared example group
     """
     require "set"
 
-    shared_examples_for "a collection object" do
+    shared_examples "a collection object" do
       describe "<<" do
         it "adds objects to the end of the collection" do
           collection << 1
@@ -86,28 +90,28 @@ Feature: shared example group
     end
 
     describe Array do
-      it_should_behave_like "a collection object" do
+      it_behaves_like "a collection object" do
         let(:collection) { Array.new }
       end
     end
 
     describe Set do
-      it_should_behave_like "a collection object" do
+      it_behaves_like "a collection object" do
         let(:collection) { Set.new }
       end
     end
     """
-    When I run "rspec shared_example_group_spec.rb --format documentation"
+    When I run `rspec shared_example_group_spec.rb --format documentation`
     Then the examples should all pass
     And the output should contain:
       """
       Array
-        it should behave like a collection object
+        behaves like a collection object
           <<
             adds objects to the end of the collection
 
       Set
-        it should behave like a collection object
+        behaves like a collection object
           <<
             adds objects to the end of the collection
       """
@@ -115,7 +119,7 @@ Feature: shared example group
   Scenario: Passing parameters to a shared example group
     Given a file named "shared_example_group_params_spec.rb" with:
     """
-    shared_examples_for "a measurable object" do |measurement, measurement_methods|
+    shared_examples "a measurable object" do |measurement, measurement_methods|
       measurement_methods.each do |measurement_method|
         it "should return #{measurement} from ##{measurement_method}" do
           subject.send(measurement_method).should == measurement
@@ -133,7 +137,7 @@ Feature: shared example group
       it_should_behave_like "a measurable object", 6, [:size, :length]
     end
     """
-    When I run "rspec shared_example_group_params_spec.rb --format documentation"
+    When I run `rspec shared_example_group_params_spec.rb --format documentation`
     Then the examples should all pass
     And the output should contain:
       """
@@ -155,7 +159,7 @@ Feature: shared example group
         c.alias_it_should_behave_like_to :it_has_behavior, 'has behavior:'
       end
 
-      shared_examples_for 'sortability' do
+      shared_examples 'sortability' do
         it 'responds to <=>' do
           sortable.should respond_to(:<=>)
         end
@@ -167,7 +171,7 @@ Feature: shared example group
         end
       end
       """
-    When I run "rspec shared_example_group_spec.rb --format documentation"
+    When I run `rspec shared_example_group_spec.rb --format documentation`
     Then the examples should all pass
     And the output should contain:
       """

data/features/expectation_framework_integration/configure_expectation_framework.feature

@@ -9,6 +9,10 @@ Feature: configure expectation framework
     * minitest assertions in ruby 1.9
   * rspec/expecations _and_ stlib assertions
 
+  Note that when you do not use rspec-expectations, you must explicitly
+  provide a description to every example.  You cannot rely on the generated
+  descriptions provided by rspec-expectations.
+
   Scenario: configure rspec-expectations (explicitly)
     Given a file named "example_spec.rb" with:
       """
@@ -22,7 +26,7 @@ Feature: configure expectation framework
         end
       end
       """
-    When I run "rspec example_spec.rb"
+    When I run `rspec example_spec.rb`
     Then the examples should all pass
 
   Scenario: configure test/unit assertions
@@ -36,10 +40,17 @@ Feature: configure expectation framework
         it "is greater than 4" do
           assert 5 > 4, "expected 5 to be greater than 4"
         end
+
+        specify { assert 5 < 6 }
       end
       """
-    When I run "rspec example_spec.rb"
-    Then the examples should all pass
+    When I run `rspec example_spec.rb`
+    Then the output should contain "2 examples, 1 failure"
+     And the output should contain:
+       """
+            NotImplementedError:
+              Generated descriptions are only supported when you use rspec-expectations.
+       """
 
   Scenario: configure rspec/expecations AND test/unit assertions
     Given a file named "example_spec.rb" with:
@@ -58,5 +69,5 @@ Feature: configure expectation framework
         end
       end
       """
-    When I run "rspec example_spec.rb"
+    When I run `rspec example_spec.rb`
     Then the examples should all pass

data/features/filtering/exclusion_filters.feature

@@ -2,6 +2,9 @@ Feature: exclusion filters
 
   You can exclude examples from a run by declaring an exclusion filter and
   then tagging examples, or entire groups, with that filter.
+
+  If you set the `treat_symbols_as_metadata_keys_with_true_values` config option
+  to `true`, you can specify metadata using only symbols.
   
   Scenario: exclude an example
     Given a file named "spec/sample_spec.rb" with:
@@ -20,7 +23,7 @@ Feature: exclusion filters
         end
       end
       """
-    When I run "rspec ./spec/sample_spec.rb --format doc"
+    When I run `rspec ./spec/sample_spec.rb --format doc`
     Then the output should contain "does one thing"
     And the output should not contain "does another thing"
 
@@ -44,7 +47,7 @@ Feature: exclusion filters
         end
       end
       """
-    When I run "rspec ./spec/sample_spec.rb --format doc"
+    When I run `rspec ./spec/sample_spec.rb --format doc`
     Then the output should contain "group 2 example 1"
     And  the output should not contain "group 1 example 1"
     And  the output should not contain "group 1 example 2"
@@ -77,7 +80,7 @@ Feature: exclusion filters
         end
       end
       """
-    When I run "rspec ./spec/sample_spec.rb --format doc"
+    When I run `rspec ./spec/sample_spec.rb --format doc`
     Then the output should match /No examples were matched. Perhaps \{.*:broken=>true.*\} is excluding everything?/
     And  the examples should all pass
     And  the output should not contain "group 1"
@@ -108,8 +111,29 @@ Feature: exclusion filters
         end
       end
       """
-    When I run "rspec ./spec/before_after_all_exclusion_filter_spec.rb"
+    When I run `rspec ./spec/before_after_all_exclusion_filter_spec.rb`
     Then the output should contain "before all in included group"
      And the output should contain "after all in included group"
      And the output should not contain "before all in excluded group"
      And the output should not contain "after all in excluded group"
+
+  Scenario: Use symbols as metadata
+    Given a file named "symbols_as_metadata_spec.rb" with:
+      """
+      RSpec.configure do |c|
+        c.treat_symbols_as_metadata_keys_with_true_values = true
+        c.filter_run_excluding :broken
+      end
+
+      describe "something" do
+        it "does one thing" do
+        end
+
+        # tag example for exclusion by adding metadata
+        it "does another thing", :broken do
+        end
+      end
+      """
+    When I run `rspec symbols_as_metadata_spec.rb --format doc`
+    Then the output should contain "does one thing"
+    And the output should not contain "does another thing"

data/features/filtering/{implicit_filters.feature → if_and_unless.feature}

@@ -1,4 +1,4 @@
-Feature: implicit filters
+Feature: :if and :unless
 
   The `:if` and `:unless` metadata keys can be used to filter examples without
   needing to configure an exclusion filter.
@@ -24,7 +24,7 @@ Feature: implicit filters
         it("no :if group no :if example") { }
       end
       """
-    When I run "rspec implicit_if_filter_spec.rb --format doc"
+    When I run `rspec implicit_if_filter_spec.rb --format doc`
     Then the output should contain all of these:
       | :if => true group :if => true example  |
       | :if => true group no :if example       |
@@ -58,7 +58,7 @@ Feature: implicit filters
         it("no :unless group no :unless example") { }
       end
       """
-    When I run "rspec implicit_unless_filter_spec.rb --format doc"
+    When I run `rspec implicit_unless_filter_spec.rb --format doc`
     Then the output should contain all of these:
       | :unless => true group :unless => false example  |
       | :unless => false group :unless => false example |
@@ -94,7 +94,7 @@ Feature: implicit filters
         it("unfocused :unless => false example", :unless => false) { }
       end
       """
-    When I run "rspec explicit_inclusion_filter_spec.rb --format doc"
+    When I run `rspec explicit_inclusion_filter_spec.rb --format doc`
     Then the output should contain all of these:
       | focused example                  |
       | focused :if => true example      |
@@ -127,7 +127,7 @@ Feature: implicit filters
         it("excluded :unless => false example", :unless => false) { }
       end
       """
-    When I run "rspec explicit_exclusion_filter_spec.rb --format doc"
+    When I run `rspec explicit_exclusion_filter_spec.rb --format doc`
     Then the output should contain all of these:
       | included example                  |
       | included :if => true example      |
@@ -156,11 +156,13 @@ Feature: implicit filters
         it(":unless => :exclude_me_for_unless example", :unless => :exclude_me_for_unless) { }
       end
       """
-    When I run "rspec override_implicit_filters_spec.rb --format doc"
+    When I run `rspec override_implicit_filters_spec.rb --format doc`
     Then the output should contain all of these:
       | :if => true example      |
       | :if => false example     |
       | :unless => true example  |
       | :unless => false example |
-    And the output should not contain "exclude_me"
+    And the output should not contain any of these:
+      | :if => :exclude_me example                |
+      | :unless => :exclude_me_for_unless example |