tuktuk-rails 0.0.6 → 0.0.7

data/vendor/bundle/ruby/2.0.0/gems/rspec-core-2.14.7/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:
+      """ruby
+      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:
+      """ruby
+      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/vendor/bundle/ruby/2.0.0/gems/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/vendor/bundle/ruby/2.0.0/gems/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/vendor/bundle/ruby/2.0.0/gems/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/vendor/bundle/ruby/2.0.0/gems/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/vendor/bundle/ruby/2.0.0/gems/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/vendor/bundle/ruby/2.0.0/gems/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