rspec-core 2.13.1 → 2.14.0.rc1

data/features/configuration/read_options_from_file.feature

@@ -2,12 +2,15 @@ Feature: read command line configuration options from files
 
   RSpec reads command line configuration options from files in two different
   locations:
-  
-    Local:  "./.rspec" (i.e. in the project's root directory)
-    Global: "~/.rspec" (i.e. in the user's home directory)
 
-  Options declared in the local file override those in the global file, while
-  those declared in RSpec.configure will override any ".rspec" file.
+    Local: `./.rspec-local` (i.e. in the project's root directory, can be gitignored)
+    Project:  `./.rspec` (i.e. in the project's root directory, usually checked into the project)
+    Global: `~/.rspec` (i.e. in the user's home directory)
+
+  Configuration options are loaded from `~/.rspec`, `.rspec`,
+  `.rspec-local`, command line switches, and the `SPEC_OPTS` environment
+  variable (listed in lowest to highest precedence; for example, an option
+  in `~/.rspec` can be overridden by an option in `.rspec-local`).
 
   Scenario: color set in .rspec
     Given a file named ".rspec" with:

data/features/configuration/run_all_when_everything_filtered.feature

@@ -1,8 +1,10 @@
 Feature: run all when everything filtered
 
-  Use the run_all_when_everything_filtered option to tell RSpec to run
-  all the specs in the case where you try to run a filtered list of
-  specs but no specs match that filter.
+  Use the run_all_when_everything_filtered option to tell RSpec to run all the
+  specs in the case where you try to run a filtered list of specs but no specs
+  match that filter. This works well when paired with an inclusion filter like
+  `:focus => true`, as it will run all the examples when none match the
+  inclusion filter.
 
     RSpec.configure { |c| c.run_all_when_everything_filtered = true }
 
@@ -12,7 +14,7 @@ Feature: run all when everything filtered
       RSpec.configure {|c| c.run_all_when_everything_filtered = true}
       """
 
-  Scenario: by default, no specs are run if they are all filtered out
+  Scenario: by default, no specs are run if they are all filtered out by an inclusion tag
     Given a file named "spec/example_spec.rb" with:
       """ruby
       describe "examples" do
@@ -26,6 +28,20 @@ Feature: run all when everything filtered
     When I run `rspec spec/example_spec.rb --tag some_tag`
     Then the output should contain "0 examples, 0 failures"
 
+  Scenario: specs are still run if they are filtered out by an exclusion tag
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      describe "examples" do
+        it "with no tag" do
+        end
+
+        it "with no tag as well" do
+        end
+      end
+      """
+    When I run `rspec spec/example_spec.rb --tag ~some_tag`
+    Then the output should contain "2 examples, 0 failures"
+
   Scenario: when the run_all_when_everything_filtered option is turned on, if there are any matches for the filtering tag, only those features are run
     Given a file named "spec/example_spec.rb" with:
       """ruby

data/features/example_groups/basic_structure.feature

@@ -14,7 +14,7 @@ Feature: basic structure (describe/it)
   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:
     """ruby

data/features/example_groups/shared_context.feature

@@ -18,7 +18,7 @@ Feature: shared context
         end
       end
       """
-  
+
   Scenario: declare shared context and include it with include_context
     Given a file named "shared_context_example.rb" with:
       """ruby

data/features/example_groups/shared_examples.feature

@@ -220,3 +220,75 @@ Feature: shared examples
         """
         1 example, 0 failures
         """
+
+  Scenario: Shared examples are nestable by context
+    Given a file named "context_specific_examples_spec.rb" with:
+      """Ruby
+      describe "shared examples" do
+        context "per context" do
+
+          shared_examples "shared examples are nestable" do
+            specify { expect(true).to eq true }
+          end
+
+          it_behaves_like "shared examples are nestable"
+        end
+      end
+      """
+    When I run `rspec context_specific_examples_spec.rb`
+    Then the output should contain:
+      """
+      1 example, 0 failures
+      """
+
+  Scenario: Shared examples are accessible from offspring contexts
+    Given a file named "context_specific_examples_spec.rb" with:
+      """Ruby
+      describe "shared examples" do
+        shared_examples "shared examples are nestable" do
+          specify { expect(true).to eq true }
+        end
+
+        context "per context" do
+          it_behaves_like "shared examples are nestable"
+        end
+      end
+      """
+    When I run `rspec context_specific_examples_spec.rb`
+    Then the output should contain:
+      """
+      1 example, 0 failures
+      """
+    And the output should not contain:
+      """
+      Accessing shared_examples defined across contexts is deprecated
+      """
+
+  Scenario: Shared examples are isolated per context
+    Given a file named "isolated_shared_examples_spec.rb" with:
+      """Ruby
+      describe "shared examples" do
+        context do
+          shared_examples "shared examples are isolated" do
+            specify { expect(true).to eq true }
+          end
+        end
+
+        context do
+          it_behaves_like "shared examples are isolated"
+        end
+      end
+      """
+    When I run `rspec isolated_shared_examples_spec.rb`
+    Then the output should contain:
+      """
+      1 example, 0 failures
+      """
+    But the output should contain:
+      """
+      Accessing shared_examples defined across contexts is deprecated
+      """
+    And the output should contain:
+      """
+      isolated_shared_examples_spec.rb:9
+      """

data/features/filtering/exclusion_filters.feature

@@ -5,7 +5,7 @@ Feature: exclusion filters
 
   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:
       """ruby
@@ -33,15 +33,15 @@ Feature: exclusion filters
       RSpec.configure do |c|
         c.filter_run_excluding :broken => true
       end
-  
+
       describe "group 1", :broken => true do
         it "group 1 example 1" do
         end
-  
+
         it "group 1 example 2" do
         end
       end
-  
+
       describe "group 2" do
         it "group 2 example 1" do
         end
@@ -51,31 +51,31 @@ Feature: exclusion filters
     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"
-  
+
   Scenario: exclude multiple groups
     Given a file named "spec/sample_spec.rb" with:
       """ruby
       RSpec.configure do |c|
         c.filter_run_excluding :broken => true
       end
-  
+
       describe "group 1", :broken => true do
         before(:all) do
           raise "you should not see me"
         end
-        
+
         it "group 1 example 1" do
         end
-  
+
         it "group 1 example 2" do
         end
       end
-  
+
       describe "group 2", :broken => true do
         before(:each) do
           raise "you should not see me"
         end
-        
+
         it "group 2 example 1" do
         end
       end

data/features/formatters/custom_formatter.feature

@@ -3,7 +3,7 @@ Feature: custom formatters
   RSpec ships with general purpose output formatters. You can tell RSpec which
   one to use using the [`--format` command line
   option]('../command_line/format_option').
-  
+
   When RSpec's built-in output formatters don't, however, give you everything
   you need, you can write your own custom formatter and tell RSpec to use that
   one instead.  The simplest way is to subclass RSpec's `BaseTextFormatter`,

data/features/hooks/before_and_after_hooks.feature

@@ -69,21 +69,21 @@ Feature: before and after hooks
           @widgets ||= []
         end
       end
-  
+
       describe Thing do
         before(:all) do
           @thing = Thing.new
         end
-  
+
         describe "initialized in before(:all)" do
           it "has 0 widgets" do
             @thing.should have(0).widgets
           end
-  
+
           it "can get accept new widgets" do
             @thing.widgets << Object.new
           end
-  
+
           it "shares state across examples" do
             @thing.should have(1).widgets
           end
@@ -187,7 +187,7 @@ Feature: before and after hooks
           @before_all = "before all"
         end
       end
-  
+
       describe "stuff in before blocks" do
         describe "with :all" do
           it "should be available in the example" do
@@ -213,21 +213,21 @@ Feature: before and after hooks
         before(:all) do
           puts "before all"
         end
-  
+
         before(:each) do
           puts "before each"
         end
-  
+
         after(:each) do
           puts "after each"
         end
-  
+
         after(:all) do
           puts "after all"
         end
-  
+
         it "gets run in order" do
-  
+
         end
       end
       """
@@ -239,7 +239,7 @@ Feature: before and after hooks
       after each
       .after all
       """
-  
+
   Scenario: before/after blocks defined in config are run in order
     Given a file named "configuration_spec.rb" with:
       """ruby
@@ -249,28 +249,28 @@ Feature: before and after hooks
         config.before(:suite) do
           puts "before suite"
         end
-  
+
         config.before(:all) do
           puts "before all"
         end
-  
+
         config.before(:each) do
           puts "before each"
         end
-  
+
         config.after(:each) do
           puts "after each"
         end
-  
+
         config.after(:all) do
           puts "after all"
         end
-  
+
         config.after(:suite) do
           puts "after suite"
         end
       end
-  
+
       describe "ignore" do
         example "ignore" do
         end
@@ -294,7 +294,7 @@ Feature: before and after hooks
         before(:all) do
           puts "outer before all"
         end
-  
+
         example "in outer group" do
         end
 
@@ -306,7 +306,7 @@ Feature: before and after hooks
           before(:all) do
             puts "inner before all"
           end
-          
+
           example "in nested group" do
           end
 

data/features/mock_framework_integration/use_any_framework.feature

@@ -5,14 +5,14 @@ Feature: mock with an alternative framework
   to provide an adapter that hooks RSpec's events into those of the framework.
 
   A mock framework adapter must expose three methods:
-    
+
   * `setup_mocks_for_rspec`
     * called before each example is run
-  * `verify_mocks_for_rspec` 
+  * `verify_mocks_for_rspec`
     * called after each example is run
     * this is where message expectation failures should result in an error with
       the appropriate failure message
-  * `teardown_mocks_for_rspec` 
+  * `teardown_mocks_for_rspec`
     * called after `verify_mocks_for_rspec`
     * use this to clean up resources, restore objects to earlier state, etc
     * guaranteed to run even if there are failures
@@ -78,7 +78,7 @@ Feature: mock with an alternative framework
         end
       end
       """
-      
+
     Given a file named "example_spec.rb" with:
       """ruby
       require File.expand_path("../expector", __FILE__)
@@ -102,5 +102,5 @@ Feature: mock with an alternative framework
       """
     When I run `rspec example_spec.rb --format doc`
     Then the exit status should be 1
-    And the output should contain "2 examples, 1 failure" 
-    And the output should contain "fails when message is received (FAILED - 1)" 
+    And the output should contain "2 examples, 1 failure"
+    And the output should contain "fails when message is received (FAILED - 1)"

data/features/mock_framework_integration/use_flexmock.feature

@@ -18,7 +18,7 @@ Feature: mock with flexmock
       end
       """
     When I run `rspec example_spec.rb`
-    Then the examples should all pass 
+    Then the examples should all pass
 
   Scenario: failing message expecation
     Given a file named "example_spec.rb" with:
@@ -79,7 +79,7 @@ Feature: mock with flexmock
     Then the output should contain "1 example, 1 failure"
     And the exit status should be 1
 
-  Scenario: accessing RSpec.configuration.mock_framework.framework_name 
+  Scenario: accessing RSpec.configuration.mock_framework.framework_name
     Given a file named "example_spec.rb" with:
       """ruby
       RSpec.configure do |config|
@@ -93,4 +93,4 @@ Feature: mock with flexmock
       end
       """
     When I run `rspec example_spec.rb`
-    Then the examples should all pass 
+    Then the examples should all pass

data/features/mock_framework_integration/use_mocha.feature

@@ -18,7 +18,7 @@ Feature: mock with mocha
       end
       """
     When I run `rspec example_spec.rb`
-    Then the examples should all pass 
+    Then the examples should all pass
 
   Scenario: failing message expecation
     Given a file named "example_spec.rb" with:
@@ -79,7 +79,7 @@ Feature: mock with mocha
     Then the output should contain "1 example, 1 failure"
     And the exit status should be 1
 
-  Scenario: accessing RSpec.configuration.mock_framework.framework_name 
+  Scenario: accessing RSpec.configuration.mock_framework.framework_name
     Given a file named "example_spec.rb" with:
       """ruby
       RSpec.configure do |config|
@@ -93,5 +93,5 @@ Feature: mock with mocha
       end
       """
     When I run `rspec example_spec.rb`
-    Then the examples should all pass 
+    Then the examples should all pass
 

data/features/mock_framework_integration/use_rr.feature

@@ -18,7 +18,7 @@ Feature: mock with rr
       end
       """
     When I run `rspec example_spec.rb`
-    Then the examples should all pass 
+    Then the examples should all pass
 
   Scenario: failing message expecation
     Given a file named "example_spec.rb" with:
@@ -79,7 +79,7 @@ Feature: mock with rr
     Then the output should contain "1 example, 1 failure"
     And the exit status should be 1
 
-  Scenario: accessing RSpec.configuration.mock_framework.framework_name 
+  Scenario: accessing RSpec.configuration.mock_framework.framework_name
     Given a file named "example_spec.rb" with:
       """ruby
       RSpec.configure do |config|
@@ -93,6 +93,6 @@ Feature: mock with rr
       end
       """
     When I run `rspec example_spec.rb`
-    Then the examples should all pass 
+    Then the examples should all pass