suzuko 0.1.7

data/vendor/bundle/ruby/2.0.0/gems/simplecov-0.10.0/doc/alternate-formatters.md

@@ -0,0 +1,36 @@
+## Alternate coverage report formatters
+
+The community around simplecov provides a whole bunch of alternate formatters beyond the official
+[simplecov-html](https://github.com/colszowka/simplecov-html) gem.
+
+If you have built or found one that is missing here, please send a Pull Request for this document!
+
+#### [simplecov-badge](https://github.com/matthew342/simplecov-badge)
+*by Matt Hale*
+
+A formatter that generates a coverage badge for use in your project's readme using ImageMagick.
+
+#### [simplecov-cobertura](https://github.com/dashingrocket/simplecov-cobertura)
+*by Jesse Bowes*
+
+A formatter that generates Cobertura XML.
+
+#### [simplecov-csv](https://github.com/fguillen/simplecov-csv)
+*by Fernando Guillen*
+
+CSV formatter for SimpleCov
+
+#### [simplecov-json](https://github.com/vicentllongo/simplecov-json)
+*by Vicent Llongo*
+
+JSON formatter for SimpleCov
+
+#### [simplecov-rcov](https://github.com/fguillen/simplecov-rcov)
+*by Fernando Guillen*
+
+"The target of this formatter is to cheat on Hudson so I can use the Ruby metrics plugin with SimpleCov."
+
+#### [simplecov-single_file_reporter](https://github.com/grosser/simplecov-single_file_reporter)
+*by [Michael Grosser](http://grosser.it)*
+
+A formatter that prints the coverage of the file under test when you run a single test file.

data/vendor/bundle/ruby/2.0.0/gems/simplecov-0.10.0/doc/commercial-services.md

@@ -0,0 +1,20 @@
+## Commercial Services with SimpleCov integration
+
+There is a bunch of services that offer integration with your existing CI pipeline and SimpleCov coverage
+reports. Please note these are not associated with the SimpleCov project itself, so please report problems with
+these integrations with their respective owners.
+
+#### [codeclimate](https://github.com/codeclimate/ruby-test-reporter)
+*by [Code Climate](https://codeclimate.com/)*
+
+Upload coverage reports to [codeclimate.com](https://codeclimate.com/), a hosted software quality analysis and that also includes coverage reporting.
+
+#### [codecov](https://github.com/codecov/codecov-ruby)
+*by [Codecov](https://codecov.io/)*
+
+Upload coverage reports to [codecov.io](https://codecov.io/), a hosted coverage reporting solution.
+
+#### [coveralls](https://github.com/lemurheavy/coveralls-ruby)
+*by [Coveralls](https://coveralls.io/)*
+
+Upload coverage reports to [coveralls.io](https://coveralls.io/), a hosted coverage reporting solution.

data/vendor/bundle/ruby/2.0.0/gems/simplecov-0.10.0/doc/editor-integration.md

@@ -0,0 +1,13 @@
+## Editor integration
+
+Some editors have a graphical integration for the simplecov gem.
+
+#### [Atom Editor: coverage](https://atom.io/packages/coverage)
+*by Philip Giuliani*
+
+Adds an overview of your current test coverage to Atom.
+
+#### [cadre](https://github.com/nyarly/cadre)
+*by Judson Lester*
+
+Includes a formatter for Simplecov that emits a Vim script to mark up code files with coverage information.

data/vendor/bundle/ruby/2.0.0/gems/simplecov-0.10.0/features/config_autoload.feature

@@ -0,0 +1,46 @@
+@test_unit @rspec @config
+Feature:
+
+  If you have multiple test suites, it can be a bit cumbersome
+  to keep the configuration across them in sync. SimpleCov
+  is able to find a config file called '.simplecov' that resides
+  in your project's root and will automatically use it when
+  loaded.
+
+  This gives you the ability to configure SimpleCov just once
+  and then use the same configuration on all test suites simply
+  by doing a 'require "simplecov"'
+
+  Scenario:
+    Given a file named ".simplecov" with:
+      """
+      SimpleCov.start do
+        add_filter 'test.rb'
+        add_filter 'spec.rb'
+      end
+      """
+    Given SimpleCov for Test/Unit is configured with:
+      """
+      require 'simplecov'
+      """
+    Given SimpleCov for RSpec is configured with:
+      """
+      require 'simplecov'
+      """
+
+    When I successfully run `bundle exec rake test`
+    And I open the coverage report generated with `bundle exec rspec spec`
+    Then the report should be based upon:
+      | RSpec      |
+      | Unit Tests |
+
+    And I should see the groups:
+      | name      | coverage | files |
+      | All Files | 90.48%    | 4     |
+
+    And I should see the source files:
+      | name                                    | coverage |
+      | lib/faked_project.rb                    | 100.0 %  |
+      | lib/faked_project/some_class.rb         |  80.0 %  |
+      | lib/faked_project/framework_specific.rb |  87.5 %  |
+      | lib/faked_project/meta_magic.rb         | 100.0 %  |

data/vendor/bundle/ruby/2.0.0/gems/simplecov-0.10.0/features/config_command_name.feature

@@ -0,0 +1,45 @@
+@test_unit @rspec @merging @config
+Feature: Custom names for individual test suites
+
+  Each test suite needs a name it can be identified by. SimpleCov tries
+  best to detect Rails' Unit, Functional, Integration tests as well as regular
+  Test/Unit, RSpec and Cucumber, but if that is insufficient, each test suite
+  config can be given a custom command name using SimpleCov.command_name.
+
+  Scenario:
+    Given SimpleCov for Test/Unit is configured with:
+      """
+      require 'simplecov'
+      SimpleCov.start do
+        command_name "I'm in UR Unitz"
+      end
+      """
+    Given SimpleCov for RSpec is configured with:
+      """
+      require 'simplecov'
+      SimpleCov.start do
+        command_name "Dreck macht Speck"
+      end
+      """
+
+    When I open the coverage report generated with `bundle exec rake test`
+    Then the report should be based upon:
+      | I'm in UR Unitz |
+
+    When I open the coverage report generated with `bundle exec rspec spec`
+    Then the report should be based upon:
+      | Dreck macht Speck |
+      | I'm in UR Unitz   |
+
+  Scenario: RSpec auto detection with spec/features
+    Given SimpleCov for RSpec is configured with:
+      """
+      require 'simplecov'
+      SimpleCov.start
+      """
+    And a file named "spec/features/foobar_spec.rb" with:
+      """
+      """
+    When I open the coverage report generated with `bundle exec rspec spec`
+    Then the report should be based upon:
+      | RSpec |

data/vendor/bundle/ruby/2.0.0/gems/simplecov-0.10.0/features/config_coverage_dir.feature

@@ -0,0 +1,33 @@
+@test_unit @config
+Feature:
+
+  The output directory for test coverage can be customized
+  with the SimpleCov.coverage_dir setting. All coverage reports
+  will be put there instead of the default 'coverage' directory
+  in your project's root.
+
+  Scenario:
+    Given SimpleCov for Test/Unit is configured with:
+      """
+      require 'simplecov'
+      SimpleCov.start do
+        coverage_dir 'test/simplecov'
+      end
+      """
+
+    When I successfully run `bundle exec rake test`
+    Then a coverage report should have been generated in "test/simplecov"
+    And a directory named "coverage" should not exist
+
+  Scenario:
+    Given SimpleCov for Test/Unit is configured with:
+      """
+      require 'simplecov'
+      SimpleCov.start do
+        coverage_dir '/tmp/test/simplecov'
+      end
+      """
+
+    When I successfully run `bundle exec rake test`
+    Then a coverage report should have been generated in "/tmp/test/simplecov"
+    And a directory named "coverage" should not exist

data/vendor/bundle/ruby/2.0.0/gems/simplecov-0.10.0/features/config_deactivate_merging.feature

@@ -0,0 +1,42 @@
+@test_unit @rspec @merging @config
+Feature:
+
+  If merging of test suite results is not desired, it can be deactivated,
+  thus leading to the coverage report being overwritten with the latest results
+  of a single test suite on each run of any suite.
+
+  It's probably preferrable to generate the individual suite results into separate
+  output directories instead (see SimpleCov.coverage_dir), but it is possible :)
+
+  Scenario:
+    Given SimpleCov for Test/Unit is configured with:
+      """
+      require 'simplecov'
+      SimpleCov.start do
+        use_merging false
+      end
+      """
+    Given SimpleCov for RSpec is configured with:
+      """
+      require 'simplecov'
+      SimpleCov.start do
+        use_merging false
+      end
+      """
+
+    When I successfully run `bundle exec rake test`
+    Then a file named "coverage/index.html" should exist
+      But a file named "coverage/.resultset.json" should not exist
+
+    Given I open the coverage report
+    Then the report should be based upon:
+      | Unit Tests |
+
+    When I successfully run `bundle exec rspec spec`
+    Then a file named "coverage/index.html" should exist
+      But a file named "coverage/.resultset.json" should not exist
+
+    Given I open the coverage report
+    Then the report should be based upon:
+      | RSpec |
+

data/vendor/bundle/ruby/2.0.0/gems/simplecov-0.10.0/features/config_formatters.feature

@@ -0,0 +1,77 @@
+@test_unit @config
+Feature:
+
+  The formatter for test coverage can be customized
+  with the SimpleCov.formatter setting. There are two
+  built-in formatters:
+    SimpleCov::Formatter::SimpleFormatter is a simple
+    formatter returning a string of all files with
+    theirs coverages.
+    SimpleCov::Formatter::MultiFormatter is a formatter
+    used to call multiple formatters at once.
+
+  Scenario: With SimpleFormatter
+    Given SimpleCov for Test/Unit is configured with:
+      """
+      require 'simplecov'
+      SimpleCov.formatter = SimpleCov::Formatter::SimpleFormatter
+      SimpleCov.at_exit do
+        puts SimpleCov.result.format!
+      end
+      SimpleCov.start do
+        add_group 'Libs', 'lib/faked_project/'
+      end
+      """
+
+    When I successfully run `bundle exec rake test`
+    Then the output should contain "lib/faked_project/meta_magic.rb (coverage: 100.0%)"
+
+  Scenario: With MultiFormatter
+    Given SimpleCov for Test/Unit is configured with:
+      """
+      require 'simplecov'
+      SimpleCov.formatter = SimpleCov::Formatter::MultiFormatter[
+        SimpleCov::Formatter::SimpleFormatter,
+        Class.new do
+          def format(result)
+            raise "Unable to format"
+          end
+        end
+      ]
+
+      SimpleCov.at_exit do
+        puts SimpleCov.result.format!.join
+      end
+      SimpleCov.start do
+        add_group 'Libs', 'lib/faked_project/'
+      end
+      """
+
+    When I successfully run `bundle exec rake test`
+    Then the output should contain "lib/faked_project/meta_magic.rb (coverage: 100.0%)"
+    And the output should match /Formatter [^\s]* failed with RuntimeError: Unable to format/
+
+  Scenario: With multiple formatters
+    Given SimpleCov for Test/Unit is configured with:
+      """
+      require 'simplecov'
+      SimpleCov.formatters = [
+        SimpleCov::Formatter::SimpleFormatter,
+        Class.new do
+          def format(result)
+            raise "Unable to format"
+          end
+        end
+      ]
+
+      SimpleCov.at_exit do
+        puts SimpleCov.result.format!.join
+      end
+      SimpleCov.start do
+        add_group 'Libs', 'lib/faked_project/'
+      end
+      """
+
+    When I successfully run `bundle exec rake test`
+    Then the output should contain "lib/faked_project/meta_magic.rb (coverage: 100.0%)"
+    And the output should match /Formatter [^\s]* failed with RuntimeError: Unable to format/

data/vendor/bundle/ruby/2.0.0/gems/simplecov-0.10.0/features/config_merge_timeout.feature

@@ -0,0 +1,39 @@
+@test_unit @rspec @merging @config
+Feature:
+
+  The maximum time between resultset merges can be customized
+  using SimpleCov.merge_timeout SECONDS. This can be helpful for
+  long-running test-suites that fail to merge because of the time
+  between individual suite finishes is more then the default timeout
+  of 10 minutes.
+
+  Here, for the sake of testing the opposite case is shown, choosing
+  a merge timeout so short that the first test suite's results actually
+  are out of date when the second suite finishes and thus does not end up
+  in the report.
+
+  Scenario:
+    Given SimpleCov for Test/Unit is configured with:
+      """
+      require 'simplecov'
+      SimpleCov.start do
+        merge_timeout 5
+      end
+      """
+    Given SimpleCov for RSpec is configured with:
+      """
+      require 'simplecov'
+      SimpleCov.start do
+        merge_timeout 5
+      end
+      """
+
+    When I open the coverage report generated with `bundle exec rake test`
+    Then the report should be based upon:
+      | Unit Tests |
+
+    When I wait for 5 seconds
+    And I open the coverage report generated with `bundle exec rspec spec`
+    Then the report should be based upon:
+      | RSpec |
+

data/vendor/bundle/ruby/2.0.0/gems/simplecov-0.10.0/features/config_nocov_token.feature

@@ -0,0 +1,79 @@
+@test_unit @nocov
+Feature:
+
+  Code wrapped in # :nocov: will be ignored by coverage reports.
+  The name of the token can be configured with SimpleCov.nocov_token or SimpleCov.skip_token
+
+  Scenario: Custom nocov token using nocov_token
+    Given SimpleCov for Test/Unit is configured with:
+      """
+      require 'simplecov'
+      SimpleCov.start 'test_frameworks' do
+        nocov_token 'skippit'
+      end
+      """
+
+    Given a file named "lib/faked_project/nocov.rb" with:
+      """
+      class SourceCodeWithNocov
+        # :skippit:
+        def some_weird_code
+          never_reached
+        rescue => err
+          but no one cares about invalid ruby here
+        end
+        # :skippit:
+      end
+      """
+
+    When I open the coverage report generated with `bundle exec rake test`
+
+    Then I should see the source files:
+      | name                                    | coverage |
+      | lib/faked_project.rb                    | 100.0 %  |
+      | lib/faked_project/some_class.rb         | 80.0 %   |
+      | lib/faked_project/framework_specific.rb | 75.0 %   |
+      | lib/faked_project/meta_magic.rb         | 100.0 %  |
+      | lib/faked_project/nocov.rb              | 100.0 %  |
+
+    And there should be 5 skipped lines in the source files
+
+    And the report should be based upon:
+      | Unit Tests |
+
+  Scenario: Custom nocov token using skip_token
+    Given SimpleCov for Test/Unit is configured with:
+      """
+      require 'simplecov'
+      SimpleCov.start 'test_frameworks' do
+        skip_token 'skippit'
+      end
+      """
+
+    Given a file named "lib/faked_project/nocov.rb" with:
+      """
+      class SourceCodeWithNocov
+        # :skippit:
+        def some_weird_code
+          never_reached
+        rescue => err
+          but no one cares about invalid ruby here
+        end
+        # :skippit:
+      end
+      """
+
+    When I open the coverage report generated with `bundle exec rake test`
+
+    Then I should see the source files:
+      | name                                    | coverage |
+      | lib/faked_project.rb                    | 100.0 %  |
+      | lib/faked_project/some_class.rb         | 80.0 %   |
+      | lib/faked_project/framework_specific.rb | 75.0 %   |
+      | lib/faked_project/meta_magic.rb         | 100.0 %  |
+      | lib/faked_project/nocov.rb              | 100.0 %  |
+
+    And there should be 5 skipped lines in the source files
+
+    And the report should be based upon:
+      | Unit Tests |

data/vendor/bundle/ruby/2.0.0/gems/simplecov-0.10.0/features/config_profiles.feature

@@ -0,0 +1,44 @@
+@test_unit @config @profiles
+Feature:
+
+  In order to re-use SimpleCov settings across projects,
+  profiles can be defined that hold configuration settings
+  that can be loaded at once.
+
+  Background:
+    Given SimpleCov for Test/Unit is configured with:
+      """
+      require 'simplecov'
+      """
+
+  Scenario: Defining and using a custom profile
+    Given a file named ".simplecov" with:
+      """
+      SimpleCov.profiles.define 'custom_command' do
+        command_name "Profile Command"
+      end
+
+      SimpleCov.start do
+        load_profile 'test_frameworks'
+        load_profile 'custom_command'
+      end
+      """
+
+    When I open the coverage report generated with `bundle exec rake test`
+    Then I should see "4 files in total."
+    And I should see "using Profile Command" within "#footer"
+
+  Scenario: Using existing profile in custom profile and supplying profile to start command
+    Given a file named ".simplecov" with:
+      """
+      SimpleCov.profiles.define 'my_profile' do
+        load_profile 'test_frameworks'
+        command_name "My Profile"
+      end
+
+      SimpleCov.start 'my_profile'
+      """
+
+    When I open the coverage report generated with `bundle exec rake test`
+    Then I should see "4 files in total."
+    And I should see "using My Profile" within "#footer"

data/vendor/bundle/ruby/2.0.0/gems/simplecov-0.10.0/features/config_project_name.feature

@@ -0,0 +1,27 @@
+@test_unit @config
+Feature:
+
+  SimpleCov guesses the project name from the project root dir's name.
+  If this is not sufficient for you, you can specify a custom name using
+  SimpleCov.project_name('xyz')
+
+
+  Scenario: Guessed name
+    Given SimpleCov for Test/Unit is configured with:
+      """
+      require 'simplecov'
+      SimpleCov.start
+      """
+
+    When I open the coverage report generated with `bundle exec rake test`
+    Then I should see "Code coverage for Project" within "title"
+
+  Scenario: Custom name
+    Given SimpleCov for Test/Unit is configured with:
+      """
+      require 'simplecov'
+      SimpleCov.start { project_name "Superfancy 2.0" }
+      """
+
+    When I open the coverage report generated with `bundle exec rake test`
+    Then I should see "Code coverage for Superfancy 2.0" within "title"

data/vendor/bundle/ruby/2.0.0/gems/simplecov-0.10.0/features/config_styles.feature

@@ -0,0 +1,121 @@
+@test_unit @config
+Feature:
+
+  There's several ways to configure SimpleCov. All of those
+  config schemes below are equivalent and can be chosen by personal
+  preference or project requirements.
+
+  Background:
+    Given SimpleCov for Test/Unit is configured with:
+      """
+      require 'simplecov'
+      """
+
+  Scenario: Inside start block
+    Given a file named ".simplecov" with:
+      """
+      SimpleCov.start do
+        add_filter 'test'
+        command_name 'Config Test Runner'
+      end
+      """
+
+    When I open the coverage report generated with `bundle exec rake test`
+    Then I should see "4 files in total."
+    And I should see "using Config Test Runner" within "#footer"
+
+  Scenario: Inside start block, using instance var from outside
+    Given a file named ".simplecov" with:
+      """
+      @filter = 'test'
+      SimpleCov.start do
+        add_filter @filter
+        command_name 'Config Test Runner'
+      end
+      """
+
+    When I open the coverage report generated with `bundle exec rake test`
+    Then I should see "4 files in total."
+    And I should see "using Config Test Runner" within "#footer"
+
+  Scenario: Inside start block, using local var from outside
+    Given a file named ".simplecov" with:
+      """
+      filter = 'test'
+      SimpleCov.start do
+        add_filter filter
+        command_name 'Config Test Runner'
+      end
+      """
+
+    When I open the coverage report generated with `bundle exec rake test`
+    Then I should see "4 files in total."
+    And I should see "using Config Test Runner" within "#footer"
+
+  Scenario: Explicitly before start block
+    Given a file named ".simplecov" with:
+      """
+      SimpleCov.add_filter 'test'
+      SimpleCov.command_name 'Config Test Runner'
+      SimpleCov.start
+      """
+
+    When I open the coverage report generated with `bundle exec rake test`
+    Then I should see "4 files in total."
+    And I should see "using Config Test Runner" within "#footer"
+
+  Scenario: Explicitly after start block
+    Given a file named ".simplecov" with:
+      """
+      SimpleCov.start
+      SimpleCov.add_filter 'test'
+      SimpleCov.command_name 'Config Test Runner'
+      """
+
+    When I open the coverage report generated with `bundle exec rake test`
+    Then I should see "4 files in total."
+    And I should see "using Config Test Runner" within "#footer"
+
+  Scenario: Using configure block after start
+    Given a file named ".simplecov" with:
+      """
+      SimpleCov.start
+      SimpleCov.configure do
+        add_filter 'test'
+        command_name 'Config Test Runner'
+      end
+      """
+
+    When I open the coverage report generated with `bundle exec rake test`
+    Then I should see "4 files in total."
+    And I should see "using Config Test Runner" within "#footer"
+
+  Scenario: Using configure block before start
+    Given a file named ".simplecov" with:
+      """
+      SimpleCov.configure do
+        add_filter 'test'
+        command_name 'Config Test Runner'
+      end
+      SimpleCov.start
+      """
+
+    When I open the coverage report generated with `bundle exec rake test`
+    Then I should see "4 files in total."
+    And I should see "using Config Test Runner" within "#footer"
+
+  Scenario: Mixing configure and start block config
+    Given a file named ".simplecov" with:
+      """
+      SimpleCov.configure do
+        command_name 'Config Test Runner'
+      end
+      SimpleCov.start do
+        add_filter 'test'
+      end
+      """
+
+    When I open the coverage report generated with `bundle exec rake test`
+    Then I should see "4 files in total."
+    And I should see "using Config Test Runner" within "#footer"
+

data/vendor/bundle/ruby/2.0.0/gems/simplecov-0.10.0/features/cucumber_basic.feature

@@ -0,0 +1,29 @@
+@cucumber
+Feature:
+
+  Simply adding the basic simplecov lines to a project should get
+  the user a coverage report after running `cucumber features`
+
+  Scenario:
+    Given SimpleCov for Cucumber is configured with:
+      """
+      require 'simplecov'
+      SimpleCov.start
+      """
+
+    When I open the coverage report generated with `bundle exec cucumber features`
+    Then I should see the groups:
+      | name      | coverage | files |
+      | All Files | 91.23%   | 6     |
+
+    And I should see the source files:
+      | name                                    | coverage |
+      | lib/faked_project.rb                    | 100.0 %  |
+      | lib/faked_project/some_class.rb         | 80.0 %   |
+      | lib/faked_project/framework_specific.rb | 75.0 %   |
+      | lib/faked_project/meta_magic.rb         | 100.0 %  |
+      | features/step_definitions/my_steps.rb   | 100.0 %  |
+      | features/support/simplecov_config.rb    | 100.0 %  |
+
+    And the report should be based upon:
+      | Cucumber Features |