syllable_counter 0.0.1 → 1.0.0

data/vendor/bundle/gems/rspec-core-2.14.5/features/command_line/line_number_option.feature

@@ -0,0 +1,58 @@
+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
+          9.should be > 8
+        end
+
+        it "should be < 10" do
+          9.should be < 10
+        end
+
+        it "should be 3 squared" do
+          9.should 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 { should be > 8 }
+
+        it { should 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/vendor/bundle/gems/rspec-core-2.14.5/features/command_line/order.feature

@@ -0,0 +1,29 @@
+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 `default` and `rand`:
+
+  Default is:
+
+    * files are ordered based on the underlying file system's order (typically
+      case-sensitive alpha on *nix OS's and case-insenstive alpha in Windows)
+    * groups/examples are loaded in the order in which they are declared
+
+  Use `rand` to randomize the order of files, groups within files, 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 default
+      --order rand
+      --order rand:123
+      --seed 123 # same as --order rand:123
+
+  The `default` 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.

data/vendor/bundle/gems/rspec-core-2.14.5/features/command_line/pattern_option.feature

@@ -0,0 +1,49 @@
+Feature: pattern option
+
+  By default, RSpec loads files matching the pattern:
+
+      "spec/**/*_spec.rb"
+
+  Use the `--pattern` option to declare a different pattern.
+
+  Scenario: default pattern
+    Given a file named "spec/example_spec.rb" with:
+      """ruby
+      describe "addition" do
+        it "adds things" do
+          (1 + 2).should eq(3)
+        end
+      end
+      """
+    When I run `rspec`
+    Then the output should contain "1 example, 0 failures"
+
+  Scenario: override the default pattern on the command line
+    Given a file named "spec/example.spec" with:
+      """ruby
+      describe "addition" do
+        it "adds things" do
+          (1 + 2).should eq(3)
+        end
+      end
+      """
+    When I run `rspec --pattern "spec/**/*.spec"`
+    Then the output should contain "1 example, 0 failures"
+
+  Scenario: override the default pattern in configuration
+    Given a file named "spec/spec_helper.rb" with:
+      """ruby
+        RSpec.configure do |config|
+          config.pattern << ',**/*.spec'
+        end
+      """
+    And a file named "spec/example.spec" with:
+      """ruby
+      describe "addition" do
+        it "adds things" do
+          (1 + 2).should eq(3)
+        end
+      end
+      """
+    When I run `rspec -rspec_helper`
+    Then the output should contain "1 example, 0 failures"

data/vendor/bundle/gems/rspec-core-2.14.5/features/command_line/rake_task.feature

@@ -0,0 +1,122 @@
+Feature: rake task
+
+  RSpec ships with a rake task with a number of useful options
+
+  Scenario: default options with passing spec (prints command and exit status is 0)
+    Given a file named "Rakefile" with:
+      """ruby
+      require 'rspec/core/rake_task'
+
+      RSpec::Core::RakeTask.new(:spec)
+
+      task :default => :spec
+      """
+    And a file named "spec/thing_spec.rb" with:
+      """ruby
+      describe "something" do
+        it "does something" do
+          # pass
+        end
+      end
+      """
+    When I run `rake`
+    Then the output should match /(ruby|rbx) -S rspec/
+    Then the exit status should be 0
+
+  Scenario: default options with failing spec (exit status is 1)
+    Given a file named "Rakefile" with:
+      """ruby
+      require 'rspec/core/rake_task'
+
+      RSpec::Core::RakeTask.new(:spec)
+
+      task :default => :spec
+      """
+    And a file named "spec/thing_spec.rb" with:
+      """ruby
+      describe "something" do
+        it "does something" do
+          fail
+        end
+      end
+      """
+    When I run `rake`
+    Then the exit status should be 1
+
+  Scenario: fail_on_error = false with failing spec (exit status is 0)
+    Given a file named "Rakefile" with:
+      """ruby
+      require 'rspec/core/rake_task'
+
+      RSpec::Core::RakeTask.new(:spec) do |t|
+        t.fail_on_error = false
+      end
+
+      task :default => :spec
+      """
+    And a file named "spec/thing_spec.rb" with:
+      """ruby
+      describe "something" do
+        it "does something" do
+          fail
+        end
+      end
+      """
+    When I run `rake`
+    Then the exit status should be 0
+
+  Scenario: rspec_opts is specified in order to pass args to the rspec command
+    Given a file named "Rakefile" with:
+      """ruby
+      require 'rspec/core/rake_task'
+
+      RSpec::Core::RakeTask.new(:spec) do |t|
+        t.rspec_opts = "--tag fast"
+      end
+      """
+    And a file named "spec/thing_spec.rb" with:
+      """ruby
+      describe "something" do
+        it "has a tag", :fast => true do
+          # pass
+        end
+
+        it "does not have a tag" do
+          fail
+        end
+      end
+      """
+    When I run `rake spec`
+    Then the exit status should be 0
+    Then the output should match:
+      """
+      (ruby|rbx) -S rspec ./spec/thing_spec.rb --tag fast
+      """
+
+  Scenario: rspec_opts is specified using arguments to the rake task
+    Given a file named "Rakefile" with:
+      """ruby
+      require 'rspec/core/rake_task'
+
+      RSpec::Core::RakeTask.new(:spec, :tag) do |t, task_args|
+        t.rspec_opts = "--tag #{task_args[:tag]}"
+      end
+      """
+    And a file named "spec/thing_spec.rb" with:
+      """ruby
+      describe "something" do
+        it "has a tag", :fast => true do
+          # pass
+        end
+
+        it "does not have a tag" do
+          fail
+        end
+      end
+      """
+    When I run `rake spec[fast]`
+    Then the exit status should be 0
+    Then the output should match:
+      """
+      (ruby|rbx) -S rspec ./spec/thing_spec.rb --tag fast
+      """

data/vendor/bundle/gems/rspec-core-2.14.5/features/command_line/require_option.feature

@@ -0,0 +1,43 @@
+Feature: --require option
+
+  Use the `--require` (or `-r`) option to specify a file to require
+  before running specs.
+
+  Scenario: using the --require option
+    Given a file named "logging_formatter.rb" with:
+      """ruby
+      require "rspec/core/formatters/base_text_formatter"
+      require 'delegate'
+
+      class LoggingFormatter < RSpec::Core::Formatters::BaseTextFormatter
+        def initialize(output)
+          super LoggingIO.new(output)
+        end
+
+        class LoggingIO < SimpleDelegator
+          def initialize(output)
+            @file = File.new('rspec.log', 'w')
+            super
+          end
+
+          def puts(message)
+            [@file, __getobj__].each { |out| out.puts message }
+          end
+
+          def close
+            @file.close
+          end
+        end
+      end
+      """
+    And a file named "spec/example_spec.rb" with:
+      """ruby
+      describe "an embarassing situation" do
+        it "happens to everyone" do
+        end
+      end
+      """
+    When I run `rspec --require ./logging_formatter.rb --format LoggingFormatter`
+    Then the output should contain "1 example, 0 failures"
+    And  the file "rspec.log" should contain "1 example, 0 failures"
+    And  the exit status should be 0

data/vendor/bundle/gems/rspec-core-2.14.5/features/command_line/ruby.feature

@@ -0,0 +1,22 @@
+Feature: run with ruby command
+
+  You can use the `ruby` command to run specs. You just need to require
+  `rspec/autorun`.
+
+  Generally speaking, you're better off using the `rspec` command, which
+  requires `rspec/autorun` for you, but some tools only work with the `ruby`
+  command.
+
+  Scenario:
+    Given a file named "example_spec.rb" with:
+      """ruby
+      require 'rspec/autorun'
+
+      describe 1 do
+        it "is < 2" do
+          1.should be < 2
+        end
+      end
+      """
+    When I run `ruby example_spec.rb`
+    Then the output should contain "1 example, 0 failures"

data/vendor/bundle/gems/rspec-core-2.14.5/features/command_line/tag.feature

@@ -0,0 +1,98 @@
+Feature: --tag option
+
+  Use the --tag (or -t) option to filter the examples by tags.
+
+  The tag can be a simple name or a name:value pair. In the first case,
+  examples with :name => true will be filtered. In the second case, examples
+  with :name => value will be filtered, where value is always a string.  In
+  both cases, name is converted to a symbol.
+
+  Tags can also be used to exclude examples by adding a ~ before the tag.  For
+  example ~tag will exclude all examples marked with :tag => true and
+  ~tag:value will exclude all examples marked with :tag => value.
+
+  To be compatible with the Cucumber syntax, tags can optionally start with
+  an @ symbol, which will be ignored.
+
+  Background:
+    Given a file named "tagged_spec.rb" with:
+      """ruby
+      describe "group with tagged specs" do
+        it "example I'm working now", :focus => true do; end
+        it "special example with string", :type => 'special' do; end
+        it "special example with symbol", :type => :special do; end
+        it "slow example", :skip => true do; end
+        it "ordinary example", :speed => 'slow' do; end
+        it "untagged example" do; end
+      end
+      """
+
+  Scenario: filter examples with non-existent tag
+    When I run `rspec . --tag mytag`
+    Then the process should succeed even though no examples were run
+
+  Scenario: filter examples with a simple tag
+    When I run `rspec . --tag focus`
+    Then the output should contain "include {:focus=>true}"
+    And the examples should all pass
+
+  Scenario: filter examples with a simple tag and @
+    When I run `rspec . --tag @focus`
+    Then the output should contain "include {:focus=>true}"
+    Then the examples should all pass
+
+  Scenario: filter examples with a name:value tag
+    When I run `rspec . --tag type:special`
+    Then the output should contain:
+      """
+      include {:type=>"special"}
+      """
+    And the output should contain "2 examples"
+    And the examples should all pass
+
+  Scenario: filter examples with a name:value tag and @
+    When I run `rspec . --tag @type:special`
+    Then the output should contain:
+      """
+      include {:type=>"special"}
+      """
+    And the examples should all pass
+
+  Scenario: exclude examples with a simple tag
+    When I run `rspec . --tag ~skip`
+    Then the output should contain "exclude {:skip=>true}"
+    Then the examples should all pass
+
+  Scenario: exclude examples with a simple tag and @
+    When I run `rspec . --tag ~@skip`
+    Then the output should contain "exclude {:skip=>true}"
+    Then the examples should all pass
+
+  Scenario: exclude examples with a name:value tag
+    When I run `rspec . --tag ~speed:slow`
+    Then the output should contain:
+      """
+      exclude {:speed=>"slow"}
+      """
+    Then the examples should all pass
+
+  Scenario: exclude examples with a name:value tag and @
+    When I run `rspec . --tag ~@speed:slow`
+    Then the output should contain:
+      """
+      exclude {:speed=>"slow"}
+      """
+    Then the examples should all pass
+
+  Scenario: filter examples with a simple tag, exclude examples with another tag
+    When I run `rspec . --tag focus --tag ~skip`
+    Then the output should contain "include {:focus=>true}"
+    And the output should contain "exclude {:skip=>true}"
+    And the examples should all pass
+
+  Scenario: exclude examples with multiple tags
+    When I run `rspec . --tag ~skip --tag ~speed:slow`
+    Then the output should contain one of the following:
+      | exclude {:skip=>true, :speed=>"slow"} |
+      | exclude {:speed=>"slow", :skip=>true} |
+    Then the examples should all pass

data/vendor/bundle/gems/rspec-core-2.14.5/features/command_line/warnings_option.feature

@@ -0,0 +1,29 @@
+Feature: run with warnings enabled
+
+  You can use the `--warnings` option to run specs with warnings enabled
+
+  @unsupported-on-rbx
+  Scenario:
+    Given a file named "example_spec.rb" with:
+      """ruby
+      describe do
+        it 'generates warning' do
+          @undefined
+        end
+      end
+      """
+    When I run `rspec --warnings example_spec.rb`
+    Then the output should contain "warning"
+
+  @unsupported-on-rbx
+  Scenario:
+    Given a file named "example_spec.rb" with:
+      """ruby
+      describe do
+        it 'generates warning' do
+          @undefined
+        end
+      end
+      """
+    When I run `rspec example_spec.rb`
+    Then the output should not contain "warning"