rspec-core 3.0.0.beta2 → 3.0.0.rc1

data/features/command_line/exit_status.feature

@@ -1,82 +0,0 @@
-Feature: exit status
-
-  The rspec command exits with an exit status of 0 if all examples pass,
-  and 1 if any examples fail. The failure exit code can be overridden
-  using the --failure-exit-code option.
-
-  Scenario: exit with 0 when all examples pass
-    Given a file named "ok_spec.rb" with:
-      """ruby
-      describe "ok" do
-        it "passes" do
-        end
-      end
-      """
-    When I run `rspec ok_spec.rb`
-    Then the exit status should be 0
-    And the examples should all pass
-
-  Scenario: exit with 1 when one example fails
-    Given a file named "ko_spec.rb" with:
-      """ruby
-      describe "KO" do
-        it "fails" do
-          raise "KO"
-        end
-      end
-      """
-    When I run `rspec ko_spec.rb`
-    Then the exit status should be 1
-    And the output should contain "1 example, 1 failure"
-
-  Scenario: exit with 1 when a nested examples fails
-    Given a file named "nested_ko_spec.rb" with:
-      """ruby
-      describe "KO" do
-        describe "nested" do
-          it "fails" do
-            raise "KO"
-          end
-        end
-      end
-      """
-    When I run `rspec nested_ko_spec.rb`
-    Then the exit status should be 1
-    And the output should contain "1 example, 1 failure"
-
-  Scenario: exit with 0 when no examples are run
-    Given a file named "a_no_examples_spec.rb" with:
-      """ruby
-      """
-    When I run `rspec a_no_examples_spec.rb`
-    Then the exit status should be 0
-    And the output should contain "0 examples"
-
-  Scenario: exit with 2 when one example fails and --failure-exit-code is 2
-    Given a file named "ko_spec.rb" with:
-      """ruby
-      describe "KO" do
-        it "fails" do
-          raise "KO"
-        end
-      end
-      """
-    When I run `rspec --failure-exit-code 2 ko_spec.rb`
-    Then the exit status should be 2
-    And the output should contain "1 example, 1 failure"
-
-  Scenario: exit with rspec's exit code when an at_exit hook is added upstream
-    Given a file named "exit_at_spec.rb" with:
-      """ruby
-      require 'rspec/autorun'
-      at_exit { exit(0) }
-
-      RSpec.describe "exit 0 at_exit" do
-        it "does not interfere with rspec's exit code" do
-          fail
-        end
-      end
-      """
-    When I run `ruby exit_at_spec.rb`
-    Then the exit status should be 1
-    And the output should contain "1 example, 1 failure"

data/features/command_line/fail_fast.feature

@@ -1,26 +0,0 @@
-Feature: --fail-fast
-
-  Use the `--fail-fast` option to tell RSpec to stop running the test suite on the first failed test.
-
-  You may also specify `--no-fail-fast` to turn it off (default behaviour).
-
-  Background:
-    Given a file named "fail_fast_spec.rb" with:
-      """ruby
-      describe "fail fast" do
-        it "passing test" do; end
-        it "failing test" do
-          fail
-        end
-        it "this should not be run" do; end
-      end
-      """
-
-  Scenario: Using --fail-fast
-    When I run `rspec . --fail-fast`
-    Then the output should contain ".F"
-    Then the output should not contain ".F."
-
-  Scenario: Using --no-fail-fast
-    When I run `rspec . --no-fail-fast`
-    Then the output should contain ".F."

data/features/command_line/format_option.feature

@@ -1,75 +0,0 @@
-Feature: --format option
-
-  Use the --format option to tell RSpec how to format the output.
-
-  RSpec ships with several formatters built in. By default, it uses the progress
-  formatter, which generates output like this:
-
-      ....F.....*.....
-
-  A '.' represents a passing example, 'F' is failing, and '*' is pending.
-
-  Use the documentation formatter to see the documentation strings passed to
-  `describe`, `it`, and their aliases:
-
-      $ rspec spec --format documentation
-
-  You can also specify an output target ($stdout by default) with an --out
-  option immediately following the --format option:
-
-      $ rspec spec --format documentation --out rspec.txt
-
-  Run `rspec --help` to see a listing of available formatters.
-
-  Background:
-    Given a file named "example_spec.rb" with:
-      """ruby
-      describe "something" do
-        it "does something that passes" do
-          expect(5).to eq(5)
-        end
-
-        it "does something that fails" do
-          expect(5).to eq(4)
-        end
-
-        it "does something that is pending", :pending => true do
-          expect(5).to be < 3
-        end
-      end
-      """
-
-  Scenario: progress bar format (default)
-    When I run `rspec --format progress example_spec.rb`
-    Then the output should contain ".F*"
-
-  Scenario: documentation format
-    When I run `rspec example_spec.rb --format documentation`
-    Then the output should contain:
-      """
-      something
-        does something that passes
-        does something that fails (FAILED - 1)
-        does something that is pending (PENDING: No reason given)
-      """
-
-  Scenario: documentation format saved to a file
-    When I run `rspec example_spec.rb --format documentation --out rspec.txt`
-    Then the file "rspec.txt" should contain:
-      """
-      something
-        does something that passes
-        does something that fails (FAILED - 1)
-        does something that is pending (PENDING: No reason given)
-      """
-
-  Scenario: multiple formats and output targets
-    When I run `rspec example_spec.rb --format progress --format documentation --out rspec.txt`
-    Then the output should contain ".F*"
-    And the file "rspec.txt" should contain:
-      """
-      something
-        does something that passes
-        does something that fails (FAILED - 1)
-        does something that is pending (PENDING: No reason given)
-      """

data/features/command_line/init.feature

@@ -1,57 +0,0 @@
-Feature: --init option
-
-  Use the --init option on the command line to generate conventional
-  files for an rspec project. It generates a `.rspec` and
-  `spec/spec_helper.rb` with some example settings to get you started.
-
-  Scenario: generate .rspec
-    When I run `rspec --init`
-    Then the following files should exist:
-      | .rspec |
-    And the output should contain "create   .rspec"
-
-  Scenario: .rspec file already exists
-    Given a file named ".rspec" with:
-      """
-      --color
-      """
-    When I run `rspec --init`
-    Then the output should contain "exist   .rspec"
-
-  Scenario: Accept and use the recommended settings in spec_helper (which are initially commented out).
-    Given I have a brand new project with no files
-      And I have run `rspec --init`
-     When I accept the recommended settings by removing `=begin` and `=end` from `spec/spec_helper.rb`
-      And I create "spec/addition_spec.rb" with the following content:
-        """ruby
-        RSpec.describe "Addition" do
-          it "works" do
-            expect(1 + 1).to eq(2)
-          end
-        end
-        """
-      And I create "spec/subtraction_spec.rb" with the following content:
-        """ruby
-        RSpec.describe "Subtraction" do
-          it "works" do
-            expect(1 - 1).to eq(0)
-          end
-        end
-        """
-
-     When I run `rspec`
-     Then the examples should all pass
-      And the output should not contain:
-        """
-        Addition
-          works
-        """
-
-     When I run `rspec spec/addition_spec.rb`
-     Then the examples should all pass
-      And the output should contain:
-        """
-        Addition
-          works
-        """
-

data/features/command_line/line_number_appended_to_path.feature

@@ -1,140 +0,0 @@
-Feature: line number appended to file path
-
-  To run one or more examples or groups, you can append the line number to the path, e.g.
-
-      rspec path/to/example_spec.rb:37
-
-  Background:
-    Given a file named "example_spec.rb" with:
-      """ruby
-      describe "outer group" do
-
-        it "first example in outer group" do
-
-        end
-
-        it "second example in outer group" do
-
-        end
-
-        describe "nested group" do
-
-          it "example in nested group" do
-
-          end
-
-        end
-
-      end
-      """
-    And a file named "example2_spec.rb" with:
-      """ruby
-      describe "yet another group" do
-        it "first example in second file" do
-        end
-        it "second example in second file" do
-        end
-      end
-      """
-
-  Scenario: nested groups - outer group on declaration line
-    When I run `rspec example_spec.rb:1 --format doc`
-    Then the examples should all pass
-    And the output should contain "second example in outer group"
-    And the output should contain "first example in outer group"
-    And the output should contain "example in nested group"
-
-  Scenario: nested groups - outer group inside block before example
-    When I run `rspec example_spec.rb:2 --format doc`
-    Then the examples should all pass
-    And the output should contain "second example in outer group"
-    And the output should contain "first example in outer group"
-    And the output should contain "example in nested group"
-
-  Scenario: nested groups - inner group on declaration line
-    When I run `rspec example_spec.rb:11 --format doc`
-    Then the examples should all pass
-    And the output should contain "example in nested group"
-    And the output should not contain "second example in outer group"
-    And the output should not contain "first example in outer group"
-
-  Scenario: nested groups - inner group inside block before example
-    When I run `rspec example_spec.rb:12 --format doc`
-    Then the examples should all pass
-    And the output should contain "example in nested group"
-    And the output should not contain "second example in outer group"
-    And the output should not contain "first example in outer group"
-
-  Scenario: two examples - first example on declaration line
-    When I run `rspec example_spec.rb:3 --format doc`
-    Then the examples should all pass
-    And the output should contain "first example in outer group"
-    But the output should not contain "second example in outer group"
-    And the output should not contain "example in nested group"
-
-  Scenario: two examples - first example inside block
-    When I run `rspec example_spec.rb:4 --format doc`
-    Then the examples should all pass
-    And the output should contain "first example in outer group"
-    But the output should not contain "second example in outer group"
-    And the output should not contain "example in nested group"
-
-  Scenario: two examples - first example on end
-    When I run `rspec example_spec.rb:5 --format doc`
-    Then the examples should all pass
-    And the output should contain "first example in outer group"
-    But the output should not contain "second example in outer group"
-    And the output should not contain "example in nested group"
-
-  Scenario: two examples - first example after end but before next example
-    When I run `rspec example_spec.rb:6 --format doc`
-    Then the examples should all pass
-    And the output should contain "first example in outer group"
-    But the output should not contain "second example in outer group"
-    And the output should not contain "example in nested group"
-
-  Scenario: two examples - second example on declaration line
-    When I run `rspec example_spec.rb:7 --format doc`
-    Then the examples should all pass
-    And the output should contain "second example in outer group"
-    But the output should not contain "first example in outer group"
-    And the output should not contain "example in nested group"
-
-  Scenario: two examples - second example inside block
-    When I run `rspec example_spec.rb:7 --format doc`
-    Then the examples should all pass
-    And the output should contain "second example in outer group"
-    But the output should not contain "first example in outer group"
-    And the output should not contain "example in nested group"
-
-  Scenario: two examples - second example on end
-    When I run `rspec example_spec.rb:7 --format doc`
-    Then the examples should all pass
-    And the output should contain "second example in outer group"
-    But the output should not contain "first example in outer group"
-    And the output should not contain "example in nested group"
-
-  Scenario: specified multiple times for different files
-    When I run `rspec example_spec.rb:7 example2_spec.rb:4 --format doc`
-    Then the examples should all pass
-    And the output should contain "second example in outer group"
-    And the output should contain "second example in second file"
-    But the output should not contain "first example in outer group"
-    And the output should not contain "nested group"
-    And the output should not contain "first example in second file"
-
-  Scenario: specified multiple times for the same file with multiple arguments
-    When I run `rspec example_spec.rb:7 example_spec.rb:11 --format doc`
-    Then the examples should all pass
-    And the output should contain "second example in outer group"
-    And the output should contain "nested group"
-    But the output should not contain "first example in outer group"
-    And the output should not contain "second file"
-
-  Scenario: specified multiple times for the same file with a single argument
-    When I run `rspec example_spec.rb:7:11 --format doc`
-    Then the examples should all pass
-    And the output should contain "second example in outer group"
-    And the output should contain "nested group"
-    But the output should not contain "first example in outer group"
-    And the output should not contain "second file"

data/features/command_line/line_number_option.feature

@@ -1,58 +0,0 @@
-Feature: --line_number option
-
-  To run a examples or groups by line numbers, one can use the --line_number option:
-
-      rspec path/to/example_spec.rb --line_number 37
-
-  This option can be specified multiple times.
-
-  Scenario: standard examples
-    Given a file named "example_spec.rb" with:
-      """ruby
-      require "rspec/expectations"
-
-      describe 9 do
-
-        it "should be > 8" do
-          expect(9).to be > 8
-        end
-
-        it "should be < 10" do
-          expect(9).to be < 10
-        end
-
-        it "should be 3 squared" do
-          expect(9).to be 3*3
-        end
-
-      end
-      """
-    When I run `rspec example_spec.rb --line_number 5 --format doc`
-    Then the examples should all pass
-    And the output should contain "should be > 8"
-    But the output should not contain "should be < 10"
-    And the output should not contain "should be 3*3"
-
-    When I run `rspec example_spec.rb --line_number 5 --line_number 9 --format doc`
-    Then the examples should all pass
-    And the output should contain "should be > 8"
-    And the output should contain "should be < 10"
-    But the output should not contain "should be 3*3"
-
-  Scenario: one liner
-    Given a file named "example_spec.rb" with:
-      """ruby
-      require "rspec/expectations"
-
-      describe 9 do
-
-        it { is_expected.to be > 8 }
-
-        it { is_expected.not_to be < 10 }
-
-      end
-      """
-    When I run `rspec example_spec.rb --line_number 5 --format doc`
-    Then the examples should all pass
-    Then the output should contain "should be > 8"
-    But the output should not contain "should be < 10"

data/features/command_line/order.feature

@@ -1,25 +0,0 @@
-Feature: --order (new in rspec-core-2.8)
-
-  Use the `--order` option to tell RSpec how to order the files, groups, and
-  examples. Options are `defined` and `rand`.
-
-  `defined` is the default, which executes groups and examples in the
-  order they are defined as the spec files are loaded.
-
-  Use `rand` to randomize the order of groups and examples within groups.*
-
-  * Nested groups are always run from top-level to bottom-level in order to avoid
-    executing `before(:all)` and `after(:all)` hooks more than once, but the order
-    of groups at each level is randomized.
-
-  You can also specify a seed:
-
-  <h3>Examples</h3>
-
-      --order defined
-      --order rand
-      --order rand:123
-      --seed 123 # same as --order rand:123
-
-  The `defined` option is only necessary when you have `--order rand` stored in a
-  config file (e.g. `.rspec`) and you want to override it from the command line.