simplecov 0.13.0 → 0.17.1

data/features/config_merge_timeout.feature

@@ -1,39 +0,0 @@
-@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/features/config_nocov_token.feature

@@ -1,79 +0,0 @@
-@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/features/config_profiles.feature

@@ -1,44 +0,0 @@
-@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/features/config_project_name.feature

@@ -1,27 +0,0 @@
-@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/features/config_styles.feature

@@ -1,121 +0,0 @@
-@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/features/config_tracked_files.feature

@@ -1,29 +0,0 @@
-@test_unit
-Feature:
-
-  Using the setting `tracked_files` should add files that were not
-  required to the report.
-
-  Scenario:
-    Given SimpleCov for Test/Unit is configured with:
-      """
-      require 'simplecov'
-      SimpleCov.start do
-        track_files "lib/**/*.rb"
-      end
-      """
-
-    When I open the coverage report generated with `bundle exec rake test`
-    Then I should see the groups:
-      | name      | coverage | files |
-      | All Files | 76.81%   | 7     |
-
-    And I should see the source files:
-      | name                                    | coverage |
-      | lib/faked_project.rb                    | 100.0 %  |
-      | lib/faked_project/untested_class.rb     | 0.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 %  |
-      | test/meta_magic_test.rb                 | 100.0 %  |
-      | test/some_class_test.rb                 | 100.0 %  |

data/features/cucumber_basic.feature

@@ -1,29 +0,0 @@
-@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 |

data/features/maximum_coverage_drop.feature

@@ -1,36 +0,0 @@
-@test_unit @config
-Feature:
-
-  Exit code should be non-zero if the overall coverage decreases by more than
-  the maximum_coverage_drop threshold.
-
-  Scenario:
-    Given SimpleCov for Test/Unit is configured with:
-      """
-      require 'simplecov'
-      SimpleCov.start do
-        add_filter 'test.rb'
-        maximum_coverage_drop 3.14
-      end
-      """
-
-    When I run `bundle exec rake test`
-    Then the exit status should be 0
-    And a file named "coverage/.last_run.json" should exist
-
-    Given a file named "lib/faked_project/missed.rb" with:
-      """
-      class UncoveredSourceCode
-        def foo
-          never_reached
-        rescue => err
-          but no one cares about invalid ruby here
-        end
-      end
-      """
-
-    When I run `bundle exec rake test`
-    Then the exit status should not be 0
-    And the output should contain "Coverage has dropped by 3.32% since the last time (maximum allowed: 3.14%)."
-    And a file named "coverage/.last_run.json" should exist
-

data/features/merging_test_unit_and_rspec.feature

@@ -1,44 +0,0 @@
-@test_unit @rspec @merging
-Feature:
-
-  Test suites like RSpec and Test/Unit should be merged automatically
-  when both have been run recently. The coverage report will feature
-  the joined results of all test suites that are using SimpleCov.
-
-  Scenario:
-    Given SimpleCov for Test/Unit is configured with:
-      """
-      require 'simplecov'
-      SimpleCov.start do
-        add_filter 'test.rb'
-        add_filter 'spec.rb'
-      end
-      """
-    And SimpleCov for RSpec is configured with:
-      """
-      require 'simplecov'
-      SimpleCov.start do
-        add_filter 'test.rb'
-        add_filter 'spec.rb'
-      end
-      """
-
-    When I open the coverage report generated with `bundle exec rake test`
-    Then the report should be based upon:
-      | Unit Tests |
-
-    When 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 %  |