simplecov 0.9.0 → 0.9.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 27181f8ed46248f7ebe05af087db2c6943824f83
-  data.tar.gz: 1457804d5cbd433e7c5f7b99a9b2f62c9e1c0f76
+  metadata.gz: 1d7e3a8ebe11da1e5ebea51e82ade251403405c9
+  data.tar.gz: 17db52c7595929742df4a51234ec27752b8e710e
 SHA512:
-  metadata.gz: 50f425070a5b073e7f2a26cb7dda9582cec71d9f4db4c3b50f0c13ecea000f26e6d3b6206d3978aed1ffabdc7f566b72279b1f050d648f0be4390d346787d820
-  data.tar.gz: 1ddc40490eb2c85454083fba35b1fb265f69093ba96ab2a4f5f5562d10c660564de374a656f9b8216ec30bdc11113bf20d8950845fdb315f60dd9fc0b70391cc
+  metadata.gz: 914e57ef6d9c4c74151e4e058bf491933ea279278c7780a81bdc4587a46dd5a0c53b7ba2c8e057729fda2803c03eb83f7f32e2bc87eaa0cfbef36aa64161c95e
+  data.tar.gz: 789409593bde254e7b33986c9a0c8fd1ae362319445abeb28f7c04857e1c7681ecdcf8e1b7829e61a4013927e42b9965b758c7eba823d1ecf8fe8d7e23146c18

data/.travis.yml

@@ -1,8 +1,6 @@
 language: ruby
-gemfile:
-  - gemfiles/multi_json_legacy.gemfile
-  - gemfiles/multi_json_new.gemfile
 rvm:
+  - 1.8.7
   - 1.9.3
   - 2.0.0
   - 2.1
@@ -15,7 +13,3 @@ matrix:
     - rvm: jruby
     - rvm: rbx-2
   fast_finish: true
-notifications:
-  email:
-    on_success: always
-    on_failure: always

data/CHANGELOG.md

@@ -1,11 +1,20 @@
-Unreleased ([changes](https://github.com/colszowka/simplecov/compare/v0.9.0...master))
+Unreleased ([changes](https://github.com/colszowka/simplecov/compare/v0.9.1...master))
 ====================
 
 ## Enhancements
 
+## Bugfixes
+
+
+0.9.1, 2014-09-21 ([changes](https://github.com/colszowka/simplecov/compare/v0.9.0...v0.9.1))
+====================
 
 ## Bugfixes
 
+ * In 0.9.0, we introduced a regression that made SimpleCov no-op mode fail on Ruby 1.8, while
+   dropping 1.8 support altogether is announced only for v1.0. This has been fixed.
+   See [#333](https://github.com/colszowka/simplecov/issues/333) (thanks (@sferik)
+
 
 0.9.0, 2014-07-17 ([changes](https://github.com/colszowka/simplecov/compare/v0.8.2...v0.9.0))
 ====================

data/CONTRIBUTING.md

@@ -2,16 +2,26 @@
 
 You can report issues at https://github.com/colszowka/simplecov/issues
 
- * Search existing issues for your problem, chances are someone else already reported it.
- * Please make sure you are running the latest version of simplecov. If that is not possible, 
-   please specify in your report why you can't update to the latest version.
+Search existing issues for your problem, chances are someone else already reported it.
+
  * Include the SimpleCov version you are running in your report.
- * Include your `ruby -e "puts RUBY_DESCRIPTION"`. Please also specify the gem versions of 
-   Rails and your testing framework, if applicable.
-   This is extremely important for narrowing down the cause of your problem.
+ * If you are not running the latest version (please check), and you cannot update it,
+   please specify in your report why you can't update to the latest version.
+ * Include your `ruby -e "puts RUBY_DESCRIPTION"`.
+ * Please also specify the gem versions of Rails (if applicable).
+ * Include any other coverage gems you may be using and their versions.
+ * Include how you run your tests and which testing framework or frameworks you are running.
+    - If running via rake, please ensure you are requiring SimpleCov at the top of your Rakefile
+    - Otherwise, please ensure you are requiring and starting SimpleCov before requiring any application code.
+      For example, if running via RSpec, this would be at the top of your spec_helper.
+    - Have you tried using a [`.simplecov` file](https://github.com/colszowka/simplecov#using-simplecov-for-centralized-config)?
+
+Include as much sample code as you can to help us reproduce the issue. (Inline, repo link, or gist, are fine. A failing test would help the most.)
+
+This is extremely important for narrowing down the cause of your problem.
 
 Thanks!
-   
+
 ## Making Contributions
 
 To fetch & test the library for development, do:
@@ -19,11 +29,7 @@ To fetch & test the library for development, do:
     $ git clone https://github.com/colszowka/simplecov.git
     $ cd simplecov
     $ bundle
-    $ rake appraisal:install
-    $ rake appraisal
-
-For more information on the appraisal gem (for testing against multiple gem dependency versions), please see
-https://github.com/thoughtbot/appraisal/
+    $ bundle exec rake
 
 If you want to contribute, please:
 

data/Gemfile

@@ -1,20 +1,27 @@
-source "https://rubygems.org"
-gemspec
-
-if 'Integration test (cucumber) suite is 1.9+ only'.respond_to? :encoding
-  gem 'aruba', '~> 0.6'
-  gem 'capybara', '~> 2.0'
-  gem 'poltergeist', '~> 1.1.0'
-  gem 'phantomjs', '~> 1.9'
-  gem 'cucumber', '~> 1.1'
-end
-
-# shoulda-matchers depends on rails >= 4, but that does not work with Ruby < 1.9. So, to allow CI builds on those versions,
-# we gotta stick with the 3.x line.
-gem 'activesupport', '~> 3.2.0'
+source 'https://rubygems.org'
 
 # Uncomment this to use local copy of simplecov-html in development when checked out
 # gem 'simplecov-html', :path => ::File.dirname(__FILE__) + '/../simplecov-html'
 
 # Uncomment this to use development version of html formatter from github
 # gem 'simplecov-html', :github => 'colszowka/simplecov-html'
+
+gemspec
+
+gem 'rake', '>= 10.3'
+
+group :test do
+  gem 'activesupport', '~> 3.2.0' # Older version required for Ruby 1.8.7 support
+  gem 'rspec', '>= 3.0'
+  gem 'rspec-legacy_formatters', '>= 1.0'
+  gem 'shoulda', '>= 3.5'
+  gem 'shoulda-matchers', '~> 2.0.0' # Older version required for Ruby 1.8.7 support
+end
+
+if 'Integration test (cucumber) suite is 1.9+ only'.respond_to?(:encoding)
+  gem 'aruba', '~> 0.6'
+  gem 'capybara', '~> 2.0.0'
+  gem 'poltergeist', '~> 1.1'
+  gem 'phantomjs', '~> 1.9'
+  gem 'cucumber', '~> 1.1'
+end

data/README.md

@@ -25,19 +25,29 @@ SimpleCov [![Build Status](https://secure.travis-ci.org/colszowka/simplecov.png)
 
 [![You can support the development of SimpleCov via Pledgie - thanks for your help](https://pledgie.com/campaigns/18379.png?skin_name=chrome)][Pledgie]
 
-SimpleCov is a code coverage analysis tool for Ruby. It uses [ruby's built-in Coverage][Coverage] library to gather code
-coverage data, but makes processing its results much easier by providing a clean API to filter, group, merge, format
-and display those results, thus giving you a complete code coverage suite that can be set up with just a couple lines of
+SimpleCov is a code coverage analysis tool for Ruby. It uses [Ruby's built-in Coverage][Coverage] library to gather code
+coverage data, but makes processing its results much easier by providing a clean API to filter, group, merge, format,
+and display those results, giving you a complete code coverage suite that can be set up with just a couple lines of
 code.
 
-In most cases, you'll want overall coverage results for your projects, including all types of tests, cucumber features
-etc. SimpleCov automatically takes care of this by caching and then merging results when generating reports, so your
+In most cases, you'll want overall coverage results for your projects, including all types of tests, Cucumber features,
+etc. SimpleCov automatically takes care of this by caching and merging results when generating reports, so your
 report actually includes coverage across your test suites and thereby gives you a better picture of blank spots.
 
-The official formatter of SimpleCov is packaged as a separate gem called [simplecov-html] but will be installed and configured
+The official formatter of SimpleCov is packaged as a separate gem called [simplecov-html], but will be installed and configured
 automatically when you launch SimpleCov. If you're curious, you can find it [on Github, too][simplecov-html].
 
 
+## Contact
+
+*Code and Bug Reports*
+
+* [Issue Tracker](https://github.com/colszowka/simplecov/issues)
+    * See [CONTRIBUTING](https://github.com/colszowka/simplecov/blob/master/CONTRIBUTING.md) for how to contribute along with some common problems to check out before creating an issue.
+
+*Questions, Problems, Suggestions, etc.*
+
+* [Mailing List]: https://groups.google.com/forum/#!forum/simplecov "Open mailing list for discussion and announcements on Google Groups"
 
 Getting started
 ---------------
@@ -81,8 +91,8 @@ end
 
     coverage
 
-If you're making a Rails application, SimpleCov comes with a built-in configurations (see below for information on profiles)
-which will get you started with groups for your Controllers, Views, Models and Helpers. To use it, the first two lines of
+If you're making a Rails application, SimpleCov comes with built-in configurations (see below for information on profiles)
+that will get you started with groups for your Controllers, Views, Models and Helpers. To use it, the first two lines of
 your test_helper should be like this:
 
 ```ruby
@@ -105,7 +115,7 @@ SimpleCov.start 'rails'
 
 ## Use it with any framework!
 
-Similarly to the usage with Test::Unit described above, the only thing you have to do is to add the simplecov
+Similarly to the usage with Test::Unit described above, the only thing you have to do is to add the SimpleCov
 config to the very top of your Cucumber/RSpec/whatever setup file.
 
 Add the setup code to the **top** of `features/support/env.rb` (for Cucumber) or `spec/spec_helper.rb` (for RSpec).
@@ -117,7 +127,7 @@ SimpleCov.start 'rails'
 ```
 
 You could even track what kind of code your UI testers are touching if you want to go overboard with things. SimpleCov does not
-care what kind of framework it is running in, it just looks at what code is being executed and generates a report about it.
+care what kind of framework it is running in; it just looks at what code is being executed and generates a report about it.
 
 ### Notes on specific frameworks and test utilities
 
@@ -131,7 +141,7 @@ to use SimpleCov with them. Here's an overview of the known ones:
    <b>Test/Unit 2</b>
  </td>
  <td>
-  Test Unit 2 used to mess with ARGV, leading to failure to detect the test process name in SimpleCov.
+  Test Unit 2 used to mess with ARGV, leading to a failure to detect the test process name in SimpleCov.
   <code>test-unit</code> releases 2.4.3+ (Dec 11th, 2011) should have this problem resolved.
  </td>
  <td>
@@ -144,7 +154,7 @@ to use SimpleCov with them. Here's an overview of the known ones:
    <b>Spork</b>
  </td>
  <td>
-  Because of how Spork works internally (using preforking) there used to be trouble when using SimpleCov
+  Because of how Spork works internally (using preforking), there used to be trouble when using SimpleCov
   with it, but that has apparently been resolved with a specific configuration strategy. See
   <a href="https://github.com/colszowka/simplecov/issues/42#issuecomment-4440284">this</a> comment.
  </td>
@@ -172,7 +182,7 @@ to use SimpleCov with them. Here's an overview of the known ones:
  </td>
  <td>
   A user has reported problems with the coverage report using the riot framework. If you experience
-  similar trouble please follow up on the related Github issue.
+  similar trouble please follow up on the related GitHub issue.
  </td>
  <td>
   <a href="https://github.com/colszowka/simplecov/issues/80">SimpleCov #80</a>
@@ -248,7 +258,7 @@ Filters can be used to remove selected files from your coverage data. By default
 OUTSIDE of your project's root directory - otherwise you'd end up with billions of coverage reports for source files in the
 gems you are using.
 
-Of course you can define your own to remove things like configuration files, tests or whatever you don't need in your coverage
+You can define your own to remove things like configuration files, tests or whatever you don't need in your coverage
 report.
 
 ### Defining custom filters
@@ -332,8 +342,8 @@ end
 
 ## Groups
 
-You can separate your source files into groups. For example, in a rails app, you'll want to have separate listings for
-Models, Controllers, Helpers, and Libs. Group definition works similar to Filters (and indeed also accepts custom
+You can separate your source files into groups. For example, in a Rails app, you'll want to have separate listings for
+Models, Controllers, Helpers, and Libs. Group definition works similarly to Filters (and also accepts custom
 filter classes), but source files end up in a group when the filter passes (returns true), as opposed to filtering results,
 which exclude files from results when the filter results in a true value.
 
@@ -352,10 +362,10 @@ end
 
 ## Merging results
 
-Normally, you want to have your coverage analyzed across ALL of your test suites, right?
+You normally want to have your coverage analyzed across ALL of your test suites, right?
 
 Simplecov automatically caches coverage results in your (coverage_path)/.resultset.json. Those results will then
-be automatically merged when generating the result, so when coverage is set up properly for cucumber and your
+be automatically merged when generating the result, so when coverage is set up properly for Cucumber and your
 unit / functional / integration tests, all of those test suites will be taken into account when building the
 coverage report.
 
@@ -363,15 +373,15 @@ There are two things to note here though:
 
 ### Test suite names
 
-Simplecov tries to guess the name of the currently running test suite based upon the shell command the tests are running
-on. This should work fine for Unit Tests, RSpec and Cucumber. If it fails, it will use the shell command
+SimpleCov tries to guess the name of the currently running test suite based upon the shell command the tests are running
+on. This should work fine for Unit Tests, RSpec, and Cucumber. If it fails, it will use the shell command
 that invoked the test suite as a command name.
 
-If you have some non-standard setup and still want nicely labeled test suites, you have to give Simplecov a cue what the
+If you have some non-standard setup and still want nicely labeled test suites, you have to give Simplecov a cue as to what the
 name of the currently running test suite is. You can do so by specifying SimpleCov.command_name in one test file that is
 part of your specific suite.
 
-So, to customize the suite names on a Rails app (yeah, sorry for being Rails biased, but everyone knows what
+To customize the suite names on a Rails app (yeah, sorry for being Rails-biased, but everyone knows what
 the structure of those projects is. You can apply this accordingly to the RSpecs in your Outlook-WebDAV-Calendar-Sync gem),
 you could do something like this:
 
@@ -390,7 +400,7 @@ SimpleCov.command_name "features"
 ```
 
 Note that this only has to be invoked ONCE PER TEST SUITE, so even if you have 200 unit test files, specifying it in
-some_test.rb is fair enough.
+some_test.rb is enough.
 
 [simplecov-html] prints the used test suites in the footer of the generated coverage report.
 
@@ -427,8 +437,8 @@ COVERAGE=true rake test
 
 ## Profiles
 
-By default, Simplecov's only config assumption is that you only want coverage reports for files inside your project
-root. To save you from repetitive configuration, you can use predefined blocks of configuration, called 'profiles',
+By default, SimpleCov's only config assumption is that you only want coverage reports for files inside your project
+root. To save yourself from repetitive configuration, you can use predefined blocks of configuration, called 'profiles',
 or define your own.
 
 You can then pass the name of the profile to be used as the first argument to SimpleCov.start. For example, simplecov
@@ -446,7 +456,7 @@ SimpleCov.profiles.define 'rails' do
 end
 ```
 
-As you can see, it's just a SimpleCov.configure block. In your test_helper.rb, launch simplecov with:
+As you can see, it's just a SimpleCov.configure block. In your test_helper.rb, launch SimpleCov with:
 
 ```ruby
 SimpleCov.start 'rails'
@@ -463,7 +473,7 @@ end
 ### Custom profiles
 
 You can load additional profiles with the SimpleCov.load_profile('xyz') method. This allows you to build upon an existing
-profile and customize it so you can reuse it in unit tests and cucumber features, for example.
+profile and customize it so you can reuse it in unit tests and Cucumber features. For example:
 
 ```ruby
 # lib/simplecov_custom_profile.rb
@@ -485,7 +495,7 @@ SimpleCov.start 'myprofile'
 
 ## Customizing exit behaviour
 
-You can define what simplecov should do when your test suite finishes by customizing the at_exit hook:
+You can define what SimpleCov should do when your test suite finishes by customizing the at_exit hook:
 
 ```ruby
 SimpleCov.at_exit do

data/Rakefile

@@ -2,7 +2,6 @@
 
 require 'rubygems'
 require 'bundler/setup'
-require 'appraisal'
 Bundler::GemHelper.install_tasks
 
 # See https://github.com/colszowka/simplecov/issues/171
@@ -29,4 +28,3 @@ if '1.9+'.respond_to? :encoding
 else
   task :default => [:test]
 end
-

data/lib/simplecov/defaults.rb

@@ -84,7 +84,7 @@ end
 
 # Autoload config from ~/.simplecov if present
 require 'etc'
-home_dir = Dir.home || Etc.getpwuid.dir || (user = ENV["USER"] && Dir.home(user))
+home_dir = File.expand_path('~') || Etc.getpwuid.dir || (user = ENV["USER"] && File.expand_path("~#{user}"))
 if home_dir
   global_config_path = File.join(home_dir, '.simplecov')
   load global_config_path if File.exist?(global_config_path)

data/lib/simplecov/version.rb

@@ -1,3 +1,3 @@
 module SimpleCov
-  VERSION = "0.9.0"
+  VERSION = "0.9.1"
 end

data/simplecov.gemspec

@@ -13,16 +13,10 @@ Gem::Specification.new do |gem|
   gem.summary     = gem.description
   gem.license     = "MIT"
 
-  gem.add_dependency 'multi_json'
+  gem.add_dependency 'multi_json', '~> 1.0'
   gem.add_dependency 'simplecov-html', '~> 0.8.0'
   gem.add_dependency 'docile', '~> 1.1.0'
 
-  gem.add_development_dependency 'appraisal', '~> 1.0'
-  gem.add_development_dependency 'rake', '~> 10.3'
-  gem.add_development_dependency 'rspec', '~> 3.0'
-  gem.add_development_dependency 'rspec-legacy_formatters', '~> 1.0'
-  gem.add_development_dependency 'shoulda', '~> 3.5'
-
   gem.files         = `git ls-files`.split("\n")
   gem.test_files    = `git ls-files -- {test,spec,features}/*`.split("\n")
   gem.executables   = `git ls-files -- bin/*`.split("\n").map{ |f| File.basename(f) }

data/test/helper.rb

@@ -9,10 +9,6 @@ class Test::Unit::TestCase
   def source_fixture(filename)
     File.expand_path(File.join(File.dirname(__FILE__), 'fixtures', filename))
   end
-
-  # Keep 1.8-rubies from complaining about missing tests in each file that covers only 1.9 functionality
-  def default_test
-  end
 end
 
 require 'shoulda_macros'

metadata

@@ -1,29 +1,29 @@
 --- !ruby/object:Gem::Specification
 name: simplecov
 version: !ruby/object:Gem::Version
-  version: 0.9.0
+  version: 0.9.1
 platform: ruby
 authors:
 - Christoph Olszowka
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-07-17 00:00:00.000000000 Z
+date: 2014-09-21 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: multi_json
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '0'
+        version: '1.0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '0'
+        version: '1.0'
 - !ruby/object:Gem::Dependency
   name: simplecov-html
   requirement: !ruby/object:Gem::Requirement
@@ -52,76 +52,6 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: 1.1.0
-- !ruby/object:Gem::Dependency
-  name: appraisal
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.0'
-- !ruby/object:Gem::Dependency
-  name: rake
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '10.3'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '10.3'
-- !ruby/object:Gem::Dependency
-  name: rspec
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '3.0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '3.0'
-- !ruby/object:Gem::Dependency
-  name: rspec-legacy_formatters
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.0'
-- !ruby/object:Gem::Dependency
-  name: shoulda
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '3.5'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '3.5'
 description: Code coverage for Ruby 1.9+ with a powerful configuration library and
   automatic merging of coverage across test suites
 email:
@@ -134,7 +64,6 @@ files:
 - ".rspec"
 - ".travis.yml"
 - ".yardopts"
-- Appraisals
 - CHANGELOG.md
 - CONTRIBUTING.md
 - Gemfile
@@ -175,8 +104,6 @@ files:
 - features/test_unit_groups_using_filter_class.feature
 - features/test_unit_without_simplecov.feature
 - features/unicode_compatiblity.feature
-- gemfiles/multi_json_legacy.gemfile
-- gemfiles/multi_json_new.gemfile
 - lib/simplecov.rb
 - lib/simplecov/command_guesser.rb
 - lib/simplecov/configuration.rb

data/Appraisals

@@ -1,8 +0,0 @@
-# See https://github.com/colszowka/simplecov/issues/132
-appraise "multi_json-new" do
-  gem "multi_json", ">= 1.3.4"
-end
-
-appraise "multi_json-legacy" do
-  gem "multi_json", "~> 1.0.0"
-end

data/gemfiles/multi_json_legacy.gemfile

@@ -1,13 +0,0 @@
-# This file was generated by Appraisal
-
-source "https://rubygems.org"
-
-gem "aruba", "~> 0.6"
-gem "capybara", "~> 2.0"
-gem "poltergeist", "~> 1.1.0"
-gem "phantomjs", "~> 1.9"
-gem "cucumber", "~> 1.1"
-gem "activesupport", "~> 3.2.0"
-gem "multi_json", "~> 1.0.0"
-
-gemspec :path => "../"

data/gemfiles/multi_json_new.gemfile

@@ -1,13 +0,0 @@
-# This file was generated by Appraisal
-
-source "https://rubygems.org"
-
-gem "aruba", "~> 0.6"
-gem "capybara", "~> 2.0"
-gem "poltergeist", "~> 1.1.0"
-gem "phantomjs", "~> 1.9"
-gem "cucumber", "~> 1.1"
-gem "activesupport", "~> 3.2.0"
-gem "multi_json", ">= 1.3.4"
-
-gemspec :path => "../"