dxruby_rp5 0.0.1

data/spec/vendor/rspec-core-2.14.7/features/configuration/backtrace_clean_patterns.feature

@@ -0,0 +1,102 @@
+Feature: Backtrace cleaning
+
+  To aid in diagnozing spec failures, RSpec cleans matching lines from backtraces. The default patterns cleaned are:
+
+    /\/lib\d*\/ruby\//,
+    /org\/jruby\//,
+    /bin\//,
+    /gems/,
+    /spec\/spec_helper\.rb/,
+    /lib\/rspec\/(core|expectations|matchers|mocks)/
+
+  This list can be modified or replaced with the `backtrace_clean_patterns` option. Additionally, rspec can be run with the `--backtrace` option to skip backtrace cleaning entirely.
+
+  Scenario: default configuration
+    Given a file named "spec/failing_spec.rb" with:
+    """ruby
+    describe "2 + 2" do
+      it "is 5" do
+        (2+2).should eq(5)
+      end
+    end
+    """
+    When I run `rspec`
+    Then the output should contain "1 example, 1 failure"
+    And the output should not contain "lib/rspec/expectations"
+
+  Scenario: With a custom setting for backtrace_clean_patterns
+    Given a file named "spec/spec_helper.rb" with:
+    """ruby
+    RSpec.configure do |config|
+      config.backtrace_clean_patterns = [
+        /spec_helper/
+      ]
+    end
+
+    def foo
+      "bar"
+    end
+    """
+    And a file named "spec/example_spec.rb" with:
+    """ruby
+    require 'spec_helper'
+    describe "foo" do
+      it "returns baz" do
+        foo.should eq("baz")
+      end
+    end
+    """
+    When I run `rspec`
+    Then the output should contain "1 example, 1 failure"
+    And the output should contain "lib/rspec/expectations"
+
+  Scenario: Adding a pattern
+    Given a file named "spec/matchers/be_baz_matcher.rb" with:
+    """ruby
+    RSpec::Matchers.define :be_baz do |_|
+      match do |actual|
+        actual == "baz"
+      end
+    end
+    """
+    And a file named "spec/example_spec.rb" with:
+    """ruby
+    RSpec.configure do |config|
+      config.backtrace_clean_patterns << /be_baz_matcher/
+    end
+
+    describe "bar" do
+      it "is baz" do
+        "bar".should be_baz
+      end
+    end
+    """
+    When I run `rspec`
+    Then the output should contain "1 example, 1 failure"
+    But the output should not contain "be_baz_matcher"
+    And the output should not contain "lib/rspec/expectations"
+
+  Scenario: Running with the --backtrace option
+    Given a file named "spec/matchers/be_baz_matcher.rb" with:
+    """ruby
+    RSpec::Matchers.define :be_baz do |_|
+      match do |actual|
+        actual == "baz"
+      end
+    end
+    """
+    And a file named "spec/example_spec.rb" with:
+    """ruby
+    RSpec.configure do |config|
+      config.backtrace_clean_patterns << /be_baz_matcher/
+    end
+
+    describe "bar" do
+      it "is baz" do
+        "bar".should be_baz
+      end
+    end
+    """
+    When I run `rspec --backtrace`
+    Then the output should contain "1 example, 1 failure"
+    And the output should not contain "be_baz_matcher"

data/spec/vendor/rspec-core-2.14.7/features/configuration/custom_settings.feature

@@ -0,0 +1,84 @@
+Feature: custom settings
+
+  Extensions like rspec-rails can add their own configuration settings.
+
+  Scenario: simple setting (with defaults)
+    Given a file named "additional_setting_spec.rb" with:
+      """ruby
+      RSpec.configure do |c|
+        c.add_setting :custom_setting
+      end
+
+      describe "custom setting" do
+        it "is nil by default" do
+          RSpec.configuration.custom_setting.should be_nil
+        end
+
+        it "acts false by default" do
+          RSpec.configuration.custom_setting.should be_false
+        end
+
+        it "is exposed as a predicate" do
+          RSpec.configuration.custom_setting?.should be_false
+        end
+
+        it "can be overridden" do
+          RSpec.configuration.custom_setting = true
+          RSpec.configuration.custom_setting.should be_true
+          RSpec.configuration.custom_setting?.should be_true
+        end
+      end
+      """
+    When I run `rspec ./additional_setting_spec.rb`
+    Then the examples should all pass
+
+  Scenario: default to true
+    Given a file named "additional_setting_spec.rb" with:
+      """ruby
+      RSpec.configure do |c|
+        c.add_setting :custom_setting, :default => true
+      end
+
+      describe "custom setting" do
+        it "is true by default" do
+          RSpec.configuration.custom_setting.should be_true
+        end
+
+        it "is exposed as a predicate" do
+          RSpec.configuration.custom_setting?.should be_true
+        end
+
+        it "can be overridden" do
+          RSpec.configuration.custom_setting = false
+          RSpec.configuration.custom_setting.should be_false
+          RSpec.configuration.custom_setting?.should be_false
+        end
+      end
+      """
+    When I run `rspec ./additional_setting_spec.rb`
+    Then the examples should all pass
+
+  Scenario: overridden in a subsequent RSpec.configure block
+    Given a file named "additional_setting_spec.rb" with:
+      """ruby
+      RSpec.configure do |c|
+        c.add_setting :custom_setting
+      end
+
+      RSpec.configure do |c|
+        c.custom_setting = true
+      end
+
+      describe "custom setting" do
+        it "returns the value set in the last cofigure block to get eval'd" do
+          RSpec.configuration.custom_setting.should be_true
+        end
+
+        it "is exposed as a predicate" do
+          RSpec.configuration.custom_setting?.should be_true
+        end
+      end
+      """
+    When I run `rspec ./additional_setting_spec.rb`
+    Then the examples should all pass
+

data/spec/vendor/rspec-core-2.14.7/features/configuration/default_path.feature

@@ -0,0 +1,38 @@
+Feature: default_path
+
+  As of rspec-2.7, you can just type `rspec` to run all specs that live
+  in the `spec` directory.
+
+  This is supported by a `--default_path` option, which is set to `spec` by
+  default. If you prefer to keep your specs in a different directory, or assign
+  an individual file to `--default_path`, you can do so on the command line or
+  in a configuration file (`.rspec`, `~/.rspec`, or a custom file).
+
+  NOTE: this option is not supported on `RSpec.configuration`, as it needs to
+  be set before spec files are loaded.
+
+  Scenario: run `rspec` with default default_path (`spec` directory)
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      describe "an example" do
+        it "passes" do
+        end
+      end
+      """
+    When I run `rspec`
+    Then the output should contain "1 example, 0 failures"
+
+  Scenario: run `rspec` with customized default_path
+    Given a file named ".rspec" with:
+      """
+      --default_path behavior
+      """
+    Given a file named "behavior/example_spec.rb" with:
+      """ruby
+      describe "an example" do
+        it "passes" do
+        end
+      end
+      """
+    When I run `rspec`
+    Then the output should contain "1 example, 0 failures"

data/spec/vendor/rspec-core-2.14.7/features/configuration/deprecation_stream.feature

@@ -0,0 +1,58 @@
+Feature: deprecation_stream
+
+  Define a custom output stream for warning about deprecations (default `$stderr`).
+
+    RSpec.configure {|c| c.deprecation_stream = File.open('deprecations.txt', 'w') }
+
+  or
+
+    RSpec.configure {|c| c.deprecation_stream = 'deprecations.txt' }
+
+  Background:
+    Given a file named "lib/foo.rb" with:
+      """ruby
+      class Foo
+        def bar
+          RSpec.deprecate "Foo#bar"
+        end
+      end
+      """
+
+  Scenario: default - print deprecations to $stderr
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      require "foo"
+      describe "calling a deprecated method" do
+        example { Foo.new.bar }
+      end
+      """
+    When I run `rspec spec/example_spec.rb`
+    Then the output should contain "DEPRECATION: Foo#bar is deprecated"
+
+  Scenario: configure using the path to a file
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      require "foo"
+      RSpec.configure {|c| c.deprecation_stream = 'deprecations.txt' }
+      describe "calling a deprecated method" do
+        example { Foo.new.bar }
+      end
+      """
+    When I run `rspec spec/example_spec.rb`
+    Then the output should not contain "DEPRECATION"
+    But the output should contain "1 deprecation logged to deprecations.txt"
+    And the file "deprecations.txt" should contain "Foo#bar is deprecated"
+
+  Scenario: configure using a File object
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      require "foo"
+      RSpec.configure {|c| c.deprecation_stream = File.open('deprecations.txt', 'w') }
+      describe "calling a deprecated method" do
+        example { Foo.new.bar }
+      end
+      """
+    When I run `rspec spec/example_spec.rb`
+    Then the output should not contain "DEPRECATION"
+    But the output should contain "1 deprecation logged to deprecations.txt"
+    And the file "deprecations.txt" should contain "Foo#bar is deprecated"

data/spec/vendor/rspec-core-2.14.7/features/configuration/fail_fast.feature

@@ -0,0 +1,77 @@
+Feature: fail fast
+
+  Use the fail_fast option to tell RSpec to abort the run on first failure:
+
+      RSpec.configure {|c| c.fail_fast = true}
+
+  Background:
+    Given a file named "spec/spec_helper.rb" with:
+      """ruby
+      RSpec.configure {|c| c.fail_fast = true}
+      """
+
+  Scenario: fail_fast with no failures (runs all examples)
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      describe "something" do
+        it "passes" do
+        end
+
+        it "passes too" do
+        end
+      end
+      """
+    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)
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      require "spec_helper"
+      describe "something" do
+        it "fails" do
+          fail
+        end
+
+        it "passes" do
+        end
+      end
+      """
+    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)
+    Given a file named "spec/example_1_spec.rb" with:
+      """ruby
+      require "spec_helper"
+      describe "something" do
+        it "passes" do
+        end
+
+        it "fails" do
+          fail
+        end
+      end
+
+      describe "something else" do
+        it "fails" do
+          fail
+        end
+      end
+      """
+    And a file named "spec/example_2_spec.rb" with:
+      """ruby
+      require "spec_helper"
+      describe "something" do
+        it "passes" do
+        end
+      end
+
+      describe "something else" do
+        it "fails" do
+          fail
+        end
+      end
+      """
+    When I run `rspec spec`
+    Then the output should contain "2 examples, 1 failure"

data/spec/vendor/rspec-core-2.14.7/features/configuration/failure_exit_code.feature

@@ -0,0 +1,36 @@
+Feature: failure exit code
+
+  Use the feature_exit_code option to set a custom exit code when RSpec fails.
+
+    RSpec.configure { |c| c.failure_exit_code = 42 }
+
+  Background:
+    Given a file named "spec/spec_helper.rb" with:
+      """ruby
+      RSpec.configure { |c| c.failure_exit_code = 42 }
+      """
+
+  Scenario: a failing spec with the default exit code
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      describe "something" do
+        it "fails" do
+          fail
+        end
+      end
+      """
+    When I run `rspec spec/example_spec.rb`
+    Then the exit status should be 1
+
+  Scenario: a failing spec with a custom exit code
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      require 'spec_helper'
+      describe "something" do
+        it "fails" do
+          fail
+        end
+      end
+      """
+    When I run `rspec spec/example_spec.rb`
+    Then the exit status should be 42

data/spec/vendor/rspec-core-2.14.7/features/configuration/order_and_seed.feature

@@ -0,0 +1,3 @@
+Feature: set the order and/or seed
+
+  You can set the order to run specs and specify a seed if you are running the specs using the 'random' ordering.  See <a href='../command_line/order.feature'>the documentation on the --order command line option</a> for more on this.

data/spec/vendor/rspec-core-2.14.7/features/configuration/output_stream.feature

@@ -0,0 +1,24 @@
+Feature: output_stream
+
+  Define a custom output stream (default `$stdout`).  Aliases: `:output`, `:out`.
+
+    RSpec.configure { |c| c.output_stream = File.open('saved_output', 'w') }
+
+  Background:
+    Given a file named "spec/spec_helper.rb" with:
+      """ruby
+      RSpec.configure {|c| c.output_stream = File.open('saved_output', 'w') }
+      """
+
+  Scenario: redirecting output
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      require 'spec_helper'
+      describe "an example" do
+        it "passes" do
+          true
+        end
+      end
+      """
+    When I run `rspec spec/example_spec.rb`
+    Then the file "saved_output" should contain "1 example, 0 failures"

data/spec/vendor/rspec-core-2.14.7/features/configuration/pattern.feature

@@ -0,0 +1,38 @@
+Feature: pattern
+
+  Use the pattern option to tell RSpec to look for specs in files that match a pattern other than "**/*_spec.rb".
+
+  Background:
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      describe "two specs here" do
+        it "passes" do
+        end
+
+        it "passes too" do
+        end
+      end
+      """
+    And a file named "spec/example_test.rb" with:
+      """ruby
+      describe "only one spec" do
+        it "passes" do
+        end
+      end
+      """
+
+  Scenario: by default, RSpec runs files that match "**/*_spec.rb"
+   When I run `rspec`
+   Then the output should contain "2 examples, 0 failures"
+
+  Scenario: the --pattern flag makes RSpec run files matching the specified pattern and ignore the default pattern
+   When I run `rspec -P "**/*_test.rb"`
+   Then the output should contain "1 example, 0 failures"
+
+  Scenario: the --pattern flag can be used to pass in multiple patterns, separated by comma
+   When I run `rspec -P "**/*_test.rb,**/*_spec.rb"`
+   Then the output should contain "3 examples, 0 failures"
+
+  Scenario: the --pattern flag accepts shell style glob unions
+   When I run `rspec -P "**/*_{test,spec}.rb"`
+   Then the output should contain "3 examples, 0 failures"

data/spec/vendor/rspec-core-2.14.7/features/configuration/profile.feature

@@ -0,0 +1,220 @@
+Feature: Profile examples
+
+  The `--profile` command line option (available from `RSpec.configure` as
+  `#profile_examples`), when set, will cause RSpec to dump out a list of
+  your slowest examples. By default, it prints the 10 slowest examples,
+  but you can set it to a different value to have it print more or fewer
+  slow examples. If `--fail-fast` option is used together with `--profile`
+  and there is a failure, slow examples are not shown.
+
+  Background:
+    Given a file named "spec/spec_helper.rb" with:
+      """ruby
+      """
+    And a file named "spec/example_spec.rb" with:
+      """ruby
+      require "spec_helper"
+
+      describe "something" do
+        it "sleeps for 0.1 seconds (example 1)" do
+          sleep 0.1
+          1.should == 1
+        end
+
+        it "sleeps for 0 seconds (example 2)" do
+          2.should == 2
+        end
+
+        it "sleeps for 0.15 seconds (example 3)" do
+          sleep 0.15
+          3.should == 3
+        end
+
+        it "sleeps for 0.05 seconds (example 4)" do
+          sleep 0.05
+          4.should == 4
+        end
+
+        it "sleeps for 0.05 seconds (example 5)" do
+          sleep 0.05
+          5.should == 5
+        end
+
+        it "sleeps for 0.05 seconds (example 6)" do
+          sleep 0.05
+          6.should == 6
+        end
+
+        it "sleeps for 0.05 seconds (example 7)" do
+          sleep 0.05
+          7.should == 7
+        end
+
+        it "sleeps for 0.05 seconds (example 8)" do
+          sleep 0.05
+          8.should == 8
+        end
+
+        it "sleeps for 0.05 seconds (example 9)" do
+          sleep 0.05
+          9.should == 9
+        end
+
+        it "sleeps for 0.05 seconds (example 10)" do
+          sleep 0.05
+          10.should == 10
+        end
+
+        it "sleeps for 0.05 seconds (example 11)" do
+          sleep 0.05
+          11.should == 11
+        end
+      end
+      """
+
+  Scenario: by default does not show profile
+    When I run `rspec spec`
+    Then the examples should all pass
+    And the output should not contain "example 1"
+    And the output should not contain "example 2"
+    And the output should not contain "example 3"
+    And the output should not contain "example 4"
+    And the output should not contain "example 5"
+    And the output should not contain "example 6"
+    And the output should not contain "example 7"
+    And the output should not contain "example 8"
+    And the output should not contain "example 9"
+    And the output should not contain "example 10"
+    And the output should not contain "example 11"
+
+  Scenario: setting `profile_examples` to true shows 10 examples
+    Given a file named "spec/spec_helper.rb" with:
+      """ruby
+      RSpec.configure { |c| c.profile_examples = true }
+      """
+    When I run `rspec spec`
+    Then the examples should all pass
+    And the output should contain "Top 10 slowest examples"
+    And the output should contain "example 1"
+    And the output should not contain "example 2"
+    And the output should contain "example 3"
+    And the output should contain "example 4"
+    And the output should contain "example 5"
+    And the output should contain "example 6"
+    And the output should contain "example 7"
+    And the output should contain "example 8"
+    And the output should contain "example 9"
+    And the output should contain "example 10"
+    And the output should contain "example 11"
+
+  Scenario: setting `profile_examples` to 2 shows 2 examples
+    Given a file named "spec/spec_helper.rb" with:
+      """ruby
+      RSpec.configure { |c| c.profile_examples = 2 }
+      """
+    When I run `rspec spec`
+    Then the examples should all pass
+    And the output should contain "Top 2 slowest examples"
+    And the output should contain "example 1"
+    And the output should not contain "example 2"
+    And the output should contain "example 3"
+    And the output should not contain "example 4"
+    And the output should not contain "example 5"
+    And the output should not contain "example 6"
+    And the output should not contain "example 7"
+    And the output should not contain "example 8"
+    And the output should not contain "example 9"
+    And the output should not contain "example 10"
+    And the output should not contain "example 11"
+
+  Scenario: setting profile examples through CLI
+    When I run `rspec spec --profile 2`
+    Then the examples should all pass
+    And the output should contain "Top 2 slowest examples"
+    And the output should contain "example 1"
+    And the output should not contain "example 2"
+    And the output should contain "example 3"
+    And the output should not contain "example 4"
+    And the output should not contain "example 5"
+    And the output should not contain "example 6"
+    And the output should not contain "example 7"
+    And the output should not contain "example 8"
+    And the output should not contain "example 9"
+    And the output should not contain "example 10"
+    And the output should not contain "example 11"
+
+  Scenario: Using `--no-profile` overrules config options
+    Given a file named "spec/spec_helper.rb" with:
+      """ruby
+      RSpec.configure { |c| c.profile_examples = true }
+      """
+    When I run `rspec spec --no-profile`
+    Then the examples should all pass
+    And the output should not contain "example 1"
+    And the output should not contain "example 2"
+    And the output should not contain "example 3"
+    And the output should not contain "example 4"
+    And the output should not contain "example 5"
+    And the output should not contain "example 6"
+    And the output should not contain "example 7"
+    And the output should not contain "example 8"
+    And the output should not contain "example 9"
+    And the output should not contain "example 10"
+    And the output should not contain "example 11"
+
+  Scenario: Using `--profile` with `--fail-fast` shows slow examples if everything passes
+    When I run `rspec spec --fail-fast --profile`
+    Then the examples should all pass
+    And the output should contain "Top 10 slowest examples"
+    And the output should contain "example 1"
+    And the output should not contain "example 2"
+    And the output should contain "example 3"
+    And the output should contain "example 4"
+    And the output should contain "example 5"
+    And the output should contain "example 6"
+    And the output should contain "example 7"
+    And the output should contain "example 8"
+    And the output should contain "example 9"
+    And the output should contain "example 10"
+    And the output should contain "example 11"
+
+  Scenario: Using `--profile` shows slow examples even in case of failures
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      require "spec_helper"
+
+      describe "something" do
+        it "sleeps for 0.1 seconds (example 1)" do
+          sleep 0.1
+          1.should == 1
+        end
+
+        it "fails" do
+          fail
+        end
+      end
+      """
+    When I run `rspec spec --profile`
+    Then the output should contain "2 examples, 1 failure"
+    And the output should contain "Top 2 slowest examples"
+    And the output should contain "example 1"
+
+  Scenario: Using `--profile` with `--fail-fast` doesn't show slow examples in case of failures
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      require "spec_helper"
+
+      describe "something" do
+        it "sleeps for 0.1 seconds (example 1)" do
+          sleep 0.1
+          1.should == 1
+        end
+
+        it "fails" do
+          fail
+        end
+      end
+      """
+    When I run `rspec spec --fail-fast --profile`
+    Then the output should not contain "Top 2 slowest examples"
+    And the output should not contain "example 1"