rspec-core 3.0.0.beta2 → 3.0.0.rc1

data/features/pending_and_skipped_examples/skipped_examples.feature

@@ -1,106 +0,0 @@
-Feature: skipped examples
-
-  RSpec offers a number of ways to indicate that an example should be skipped
-  and not executed.
-
-  Scenario: no implementation provided
-    Given a file named "example_without_block_spec.rb" with:
-      """ruby
-      describe "an example" do
-        it "is a skipped example"
-      end
-      """
-    When I run `rspec example_without_block_spec.rb`
-    Then the exit status should be 0
-    And the output should contain "1 example, 0 failures, 1 pending"
-    And the output should contain "Not yet implemented"
-    And the output should contain "example_without_block_spec.rb:2"
-
-  Scenario: skipping using `skip`
-    Given a file named "skipped_spec.rb" with:
-      """ruby
-      describe "an example" do
-        skip "is skipped" do
-        end
-      end
-      """
-    When I run `rspec skipped_spec.rb`
-    Then the exit status should be 0
-    And the output should contain "1 example, 0 failures, 1 pending"
-    And the output should contain:
-      """
-      Pending:
-        an example is skipped
-          # No reason given
-          # ./skipped_spec.rb:2
-      """
-
-  Scenario: skipping using `skip` inside an example
-    Given a file named "skipped_spec.rb" with:
-      """ruby
-      describe "an example" do
-        it "is skipped" do
-          skip
-        end
-      end
-      """
-    When I run `rspec skipped_spec.rb`
-    Then the exit status should be 0
-    And the output should contain "1 example, 0 failures, 1 pending"
-    And the output should contain:
-      """
-      Pending:
-        an example is skipped
-          # No reason given
-          # ./skipped_spec.rb:2
-      """
-
-  Scenario: temporarily skipping by prefixing `it`, `specify`, or `example` with an x
-    Given a file named "temporarily_skipped_spec.rb" with:
-      """ruby
-      describe "an example" do
-        xit "is skipped using xit" do
-        end
-
-        xspecify "is skipped using xspecify" do
-        end
-
-        xexample "is skipped using xexample" do
-        end
-      end
-      """
-    When I run `rspec temporarily_skipped_spec.rb`
-    Then the exit status should be 0
-    And the output should contain "3 examples, 0 failures, 3 pending"
-    And the output should contain:
-      """
-      Pending:
-        an example is skipped using xit
-          # Temporarily skipped with xit
-          # ./temporarily_skipped_spec.rb:2
-        an example is skipped using xspecify
-          # Temporarily skipped with xspecify
-          # ./temporarily_skipped_spec.rb:5
-        an example is skipped using xexample
-          # Temporarily skipped with xexample
-          # ./temporarily_skipped_spec.rb:8
-      """
-
-  Scenario: skipping using metadata
-    Given a file named "skipped_spec.rb" with:
-      """ruby
-      describe "an example" do
-        example "is skipped", :skip => true do
-        end
-      end
-      """
-    When I run `rspec skipped_spec.rb`
-    Then the exit status should be 0
-    And the output should contain "1 example, 0 failures, 1 pending"
-    And the output should contain:
-      """
-      Pending:
-        an example is skipped
-          # No reason given
-          # ./skipped_spec.rb:2
-      """

data/features/spec_files/arbitrary_file_suffix.feature

@@ -1,13 +0,0 @@
-Feature: arbitrary file suffix
-
-  Scenario: .spec
-    Given a file named "a.spec" with:
-      """ruby
-      describe "something" do
-        it "does something" do
-          expect(3).to eq(3)
-        end
-      end
-      """
-    When I run `rspec a.spec`
-    Then the examples should all pass

data/features/step_definitions/additional_cli_steps.rb

@@ -1,83 +0,0 @@
-require 'rspec/core'  # to fix annoying "undefined method `configuration' for RSpec:Module (NoMethodError)"
-
-Then /^the output should contain all of these:$/ do |table|
-  table.raw.flatten.each do |string|
-    assert_partial_output(string, all_output)
-  end
-end
-
-Then /^the output should not contain any of these:$/ do |table|
-  table.raw.flatten.each do |string|
-    expect(all_output).not_to match(regexp(string))
-  end
-end
-
-Then /^the output should contain one of the following:$/ do |table|
-  matching_output = table.raw.flatten.select do |string|
-    all_output =~ regexp(string)
-  end
-
-  expect(matching_output.count).to eq(1)
-end
-
-Then /^the example(?:s)? should(?: all)? pass$/ do
-  step %q{the output should contain "0 failures"}
-  step %q{the output should not contain "0 examples"}
-  step %q{the exit status should be 0}
-end
-
-Then /^the process should succeed even though no examples were run$/ do
-  step %q{the output should contain "0 examples, 0 failures"}
-  step %q{the exit status should be 0}
-end
-
-Then /^the backtrace\-normalized output should contain:$/ do |partial_output|
-  # ruby 1.9 includes additional stuff in the backtrace,
-  # so we need to normalize it to compare it with our expected output.
-  normalized_output = all_output.split("\n").map do |line|
-    line =~ /(^\s+# [^:]+:\d+)/ ? $1 : line # http://rubular.com/r/zDD7DdWyzF
-  end.join("\n")
-
-  expect(normalized_output).to match(regexp(partial_output))
-end
-
-Then /^the output should not contain any error backtraces$/ do
-  step %q{the output should not contain "lib/rspec/core"}
-end
-
-# This step can be generalized if it's ever used to test other colors
-Then /^the failing example is printed in magenta$/ do
-  # \e[35m = enable magenta
-  # \e[0m  = reset colors
-  expect(all_output).to include("\e[35m" + "F" + "\e[0m")
-end
-
-Given /^I have a brand new project with no files$/ do
-  in_current_dir do
-    expect(Dir["**/*"]).to eq([])
-  end
-end
-
-Given /^I have run `([^`]*)`$/ do |cmd|
-  fail_on_error = true
-  run_simple(unescape(cmd), fail_on_error)
-end
-
-When "I accept the recommended settings by removing `=begin` and `=end` from `spec/spec_helper.rb`" do
-  in_current_dir do
-    spec_helper = File.read("spec/spec_helper.rb")
-    expect(spec_helper).to include("=begin", "=end")
-
-    to_keep = spec_helper.lines.reject do |line|
-      line.start_with?("=begin") || line.start_with?("=end")
-    end
-
-    File.open("spec/spec_helper.rb", "w") { |f| f.write(to_keep.join) }
-    expect(File.read("spec/spec_helper.rb")).not_to include("=begin", "=end")
-  end
-end
-
-When /^I create "([^"]*)" with the following content:$/ do |file_name, content|
-  write_file(file_name, content)
-end
-

data/features/subject/explicit_subject.feature

@@ -1,101 +0,0 @@
-Feature: explicit subject
-
-  Use `subject` in the group scope to explicitly define the value that is
-  returned by the `subject` method in the example scope.
-
-  Note that while the examples below demonstrate how `subject` can be used as a
-  user-facing concept, we recommend that you reserve it for support of custom
-  matchers and/or extension libraries that hide its use from examples.
-
-  Scenario: subject in top level group
-    Given a file named "top_level_subject_spec.rb" with:
-      """ruby
-      describe Array, "with some elements" do
-        subject { [1,2,3] }
-        it "should have the prescribed elements" do
-          expect(subject).to eq([1,2,3])
-        end
-      end
-      """
-    When I run `rspec top_level_subject_spec.rb`
-    Then the examples should all pass
-
-  Scenario: subject in a nested group
-    Given a file named "nested_subject_spec.rb" with:
-      """ruby
-      describe Array do
-        subject { [1,2,3] }
-        describe "with some elements" do
-          it "should have the prescribed elements" do
-            expect(subject).to eq([1,2,3])
-          end
-        end
-      end
-      """
-    When I run `rspec nested_subject_spec.rb`
-    Then the examples should all pass
-
-  Scenario: access subject from before block
-    Given a file named "top_level_subject_spec.rb" with:
-      """ruby
-      describe Array, "with some elements" do
-        subject { [] }
-        before { subject.push(1,2,3) }
-        it "should have the prescribed elements" do
-          expect(subject).to eq([1,2,3])
-        end
-      end
-      """
-    When I run `rspec top_level_subject_spec.rb`
-    Then the examples should all pass
-
-  Scenario: invoke helper method from subject block
-    Given a file named "helper_subject_spec.rb" with:
-      """ruby
-      describe Array do
-        def prepared_array; [1,2,3] end
-        subject { prepared_array }
-        describe "with some elements" do
-          it "should have the prescribed elements" do
-            expect(subject).to eq([1,2,3])
-          end
-        end
-      end
-      """
-    When I run `rspec helper_subject_spec.rb`
-    Then the examples should all pass
-
-  Scenario: subject block is invoked at most once per example
-    Given a file named "nil_subject_spec.rb" with:
-      """ruby
-      describe Array do
-        describe "#[]" do
-          context "with index out of bounds" do
-            before { expect(Array).to receive(:one_two_three).once.and_return([1,2,3]) }
-            subject { Array.one_two_three[42] }
-            it { is_expected.to be_nil }
-          end
-        end
-      end
-      """
-    When I run `rspec nil_subject_spec.rb`
-    Then the examples should all pass
-
-  Scenario: subject bang method
-    Given a file named "subject_bang_spec.rb" with:
-      """ruby
-      describe Array do
-        describe '#pop' do
-          let(:prepared_array) { [1,2,3] }
-          subject! { prepared_array.pop }
-          it "removes the last value from the array" do
-            expect(prepared_array).to eq([1,2])
-          end
-          it "returns the last value of the array" do
-            expect(subject).to eq(3)
-          end
-        end
-      end
-      """
-    When I run `rspec subject_bang_spec.rb`
-    Then the examples should all pass

data/features/subject/implicit_subject.feature

@@ -1,63 +0,0 @@
-Feature: implicitly defined subject
-
-  If the first argument to the outermost example group is a class, an instance
-  of that class is exposed to each example via the `subject` method.
-
-  While the examples below demonstrate how `subject` can be used as a
-  user-facing concept, we recommend that you reserve it for support of custom
-  matchers and/or extension libraries that hide its use from examples.
-
-  Scenario: subject exposed in top level group
-    Given a file named "top_level_subject_spec.rb" with:
-      """ruby
-      describe Array do
-        it "should be empty when first created" do
-          expect(subject).to be_empty
-        end
-      end
-      """
-    When I run `rspec ./top_level_subject_spec.rb`
-    Then the examples should all pass
-
-  Scenario: subject in a nested group
-    Given a file named "nested_subject_spec.rb" with:
-      """ruby
-      describe Array do
-        describe "when first created" do
-          it "should be empty" do
-            expect(subject).to be_empty
-          end
-        end
-      end
-      """
-    When I run `rspec nested_subject_spec.rb`
-    Then the examples should all pass
-
-  Scenario: subject in a nested group with a different class (outermost wins)
-    Given a file named "nested_subject_spec.rb" with:
-      """ruby
-      class ArrayWithOneElement < Array
-        def initialize(*)
-          super
-          unshift "first element"
-        end
-      end
-
-      describe Array do
-        describe ArrayWithOneElement do
-          context "referenced as subject" do
-            it "should be empty (because it is the Array declared at the top)" do
-              expect(subject).to be_empty
-            end
-          end
-
-          context "created in the example" do
-            it "should not be empty" do
-              expect(ArrayWithOneElement.new).not_to be_empty
-            end
-          end
-        end
-      end
-      """
-    When I run `rspec nested_subject_spec.rb`
-    Then the examples should all pass

data/features/subject/one_liner_syntax.feature

@@ -1,71 +0,0 @@
-Feature: One-liner syntax
-
-  RSpec supports a one-liner syntax for setting an expectation
-  on the `subject`. RSpec will give the examples a doc string
-  that is auto-generated from the matcher used in the example.
-  This is designed specifically to help avoid duplication in
-  situations where the doc string and the matcher used in the
-  example mirror each other exactly. When used excessively,
-  it can produce documentation output that does not read well
-  or contribute to understanding the object you are describing.
-
-  This comes in two flavors:
-
-    * `is_expected` is defined simply as `expect(subject)` and is
-      designed for when you are using rspec-expectations with its
-      newer expect-based syntax.
-    * `should` was designed back when rspec-expectations only had
-      a should-based syntax. However, it continues to be available
-      and work even if the `:should` syntax is disabled (since that
-      merely removes `Object#should` but this is
-      `RSpec::Core::ExampleGroup#should`).
-
-  Note: this feature is only available when using rspec-expectations.
-
-  Scenario: implicit subject
-    Given a file named "example_spec.rb" with:
-      """ruby
-      describe Array do
-        describe "when first created" do
-          # Rather than:
-          # it "should be empty" do
-          #   subject.should be_empty
-          # end
-
-          it { should be_empty }
-          # or
-          it { is_expected.to be_empty }
-        end
-      end
-      """
-    When I run `rspec example_spec.rb --format doc`
-    Then the examples should all pass
-     And the output should contain:
-       """
-       Array
-         when first created
-           should be empty
-           should be empty
-       """
-
-  Scenario: explicit subject
-    Given a file named "example_spec.rb" with:
-      """ruby
-      describe Array do
-        describe "with 3 items" do
-          subject { [1,2,3] }
-          it { should_not be_empty }
-          # or
-          it { is_expected.not_to be_empty }
-        end
-      end
-      """
-    When I run `rspec example_spec.rb --format doc`
-    Then the examples should all pass
-     And the output should contain:
-       """
-       Array
-         with 3 items
-           should not be empty
-           should not be empty
-       """

data/features/support/env.rb

@@ -1,21 +0,0 @@
-require 'aruba/cucumber'
-
-Before do
-  if RUBY_PLATFORM =~ /java/ || defined?(Rubinius)
-    @aruba_timeout_seconds = 60
-  else
-    @aruba_timeout_seconds = 10
-  end
-end
-
-Aruba.configure do |config|
-  config.before_cmd do |cmd|
-    set_env('JRUBY_OPTS', "-X-C #{ENV['JRUBY_OPTS']}") # disable JIT since these processes are so short lived
-  end
-end if RUBY_PLATFORM == 'java'
-
-Aruba.configure do |config|
-  config.before_cmd do |cmd|
-    set_env('RBXOPT', "-Xint=true #{ENV['RBXOPT']}") # disable JIT since these processes are so short lived
-  end
-end if defined?(Rubinius)