coverband 4.0.1 → 4.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: b7f0d091dfa76cb111bc6e76be9f03a644c9f7c9
-  data.tar.gz: d326e418b2612a0fd5ea9d17786918d9da90a5df
+SHA256:
+  metadata.gz: 1e214b1bd6119046657daa64ed6d69f77f821c6c670b72e98d307ede5f08e61f
+  data.tar.gz: 469d9470799f90b5b52d53d3a630fae75b3b6bff0390375987902331878f530e
 SHA512:
-  metadata.gz: 55288f996b6d5bc015e368c6952daf867b5a21fa0f5a09fdd7bfad3f19f0b11c6e12ca912e6121e315b23a15ca1ac03629552811874f8176ee882b91aafed967
-  data.tar.gz: 37fc422e6b917dacbede5a143bc2504f1da47dbf528e3164e91661545aa2bccd1c70332a2e8783414986c5bbd89925804c28961f20f321bf0073d034c9f56eaa
+  metadata.gz: f1b0f503941ab9dbc2dee6a184fe6d6d937a5f505a5c9112ae7343197372586d6cb42df758f24effde0ee30fb359c0e2e651c64a1f5ee4c9a588a4499683dc73
+  data.tar.gz: ee700abfe4c730011dcc5c1c8521f55a2cc7ec5149e44b08187c8d09419023160a0f7c8aaba4b2aa0bb405eb13f4aeee1d8ce9cabce4860738d4ea94cac63c04

data/.gitignore

@@ -5,6 +5,8 @@
 .yardoc
 .idea/
 .ruby-version
+assets/.DS_Store
+.DS_Store
 Gemfile*lock
 InstalledFiles
 _yardoc
@@ -16,7 +18,10 @@ rdoc
 spec/reports
 test/tmp
 test/version_tmp
-tmp
+/tmp/
+temp_results
 .byebug_history
 .env
 log/
+test/unique_files
+test/rails5_dummy/tmp

data/.travis.yml

@@ -3,11 +3,17 @@ rvm:
   - "2.3"
   - "2.4"
   - "2.5"
-  - "2.6"
+  - "2.6.1"
 gemfile:
   - Gemfile
   - Gemfile.rails4
 services:
   - redis-server
 before_install:
-  - gem install bundler
+  - echo 'this is a hack to clear default bundler and force bundler 1.17.3'
+  - ls /home/travis/.rvm/gems/
+  - rm /home/travis/.rvm/gems/ruby-2.3.7@global/specifications/bundler-2.0.1.gemspec || true
+  - rm /home/travis/.rvm/gems/ruby-2.5.4@global/specifications/bundler-2.0.1.gemspec || true
+  - gem uninstall bundler || true
+  - gem install bundler -v '1.17.3'
+  - bundler --version

data/Gemfile

@@ -5,3 +5,5 @@ source 'https://rubygems.org'
 # Specify your gem's dependencies in coverband.gemspec
 gemspec
 gem 'rails', '~>5'
+# this is used for testing gem tracking
+gem 'rainbow', require: false

data/Gemfile.rails4

@@ -5,3 +5,5 @@ source 'https://rubygems.org'
 # Specify your gem's dependencies in coverband.gemspec
 gemspec
 gem 'rails', '~>4'
+# this is used for testing gem tracking
+gem 'rainbow', require: false

data/README.md

@@ -1,3 +1,5 @@
+<img src="https://raw.github.com/danmayer/coverband/master/docs/assets/logo/heads.svg?sanitize=true" width='300'>
+
 # Coverband
 
 [![Build Status](https://travis-ci.org/danmayer/coverband.svg?branch=master)](https://travis-ci.org/danmayer/coverband)
@@ -6,32 +8,39 @@
 <p align="center">
   <a href="#key-features">Key Features</a> •
   <a href="#installation">Installation</a> •
-  <a href="#configuration">Configuration</a> •
-  <a href="#coverband-demo">Coverband Demo</a> •
-  <a href="#how-to-use">How To Use</a> •
+  <a href="#coverage-report">Coverage Report</a> •
+  <a href="#verify-correct-installation">Verify Correct Installation</a> •
+  <a href="#advanced-config">Advanced Config</a> •
   <a href="#license">License</a> •
   <a href="/changes.md">Change Log / Roadmap</a>
 </p>
 
 A gem to measure production code usage, showing a counter for the number of times each line of code that is executed. Coverband allows easy configuration to collect and report on production code usage. It reports in the background via a thread or can be used as Rack middleware, or manually configured to meet any need.
 
-__Note:__ Coverband is not intended for test code coverage, for that we recommended using [SimpleCov](https://github.com/colszowka/simplecov).
+**Note:** Coverband is not intended for test code coverage, for that we recommended using [SimpleCov](https://github.com/colszowka/simplecov).
 
 ## Key Features
 
 The primary goal of Coverband is giving deep insight into your production runtime usage of your application code, while having the least impact on performance possible.
 
-* Low performance overhead
-* Very simple setup and configuration
-* Out of the box support for all standard code execution paths (web, cron, background jobs, rake tasks, etc)
-* Easy to understand actionable insights from the report
-* Development mode, offers deep insight of code usage details (number of LOC execution during single request, etc) during development.
-* Mountable web interface to easily share reports
-
+- Low performance overhead
+- Very simple setup and configuration
+- Out of the box support for all standard code execution paths (web, cron, background jobs, rake tasks, etc)
+- Easy to understand actionable insights from the report
+- Development mode, offers deep insight of code usage details (number of LOC execution during single request, etc) during development.
+- Mountable web interface to easily share reports
 
 # Installation
 
-Coverband should be near zero config for Rails apps, if you have an issue with that, please [file an issue](https://github.com/danmayer/coverband/issues).
+## Redis
+
+Coverband stores coverage data in Redis. The Redis endpoint is looked for in this order:
+
+1. `ENV['COVERBAND_REDIS_URL']`
+2. `ENV['REDIS_URL']`
+3. `localhost`
+
+The redis store can also be explicitly defined within the coverband.rb. See [advanced config](#advanced-config).
 
 ## Gem Installation
 
@@ -41,12 +50,11 @@ Add this line to your application's `Gemfile`, remember to `bundle install` afte
 gem 'coverband'
 ```
 
-## Rails
+If [tracking gem usage](#collecting-gem--library-usage), be sure to include coverband before other gems you would like to track.
 
-The Railtie integration means you shouldn't need to do anything anything else.
+## Rails
 
-* By default Coverband will try to stored data to Redis
-	* Redis endpoint is looked for in this order: `ENV['COVERBAND_REDIS_URL']`, `ENV['REDIS_URL']`, or `localhost`
+The Railtie integration means you shouldn't need to do anything anything else other than ensure coverband is required after rails within your Gemfile.
 
 ## Sinatra
 
@@ -60,137 +68,88 @@ use Coverband::Middleware
 run ActionController::Dispatcher.new
 ```
 
-# Report Generation
-
-There are two primary ways to generate and view the report
-
-## Rake Tasks
+# Coverage Report
 
-After installing the gem in Rails you should have these Rake tasks
+Coverband comes with a mountable rack app for viewing reports. For Rails this can be done in `config/routes.rb` with:
 
-```bash
-rake -T coverband
-rake coverband:coverage      # report runtime Coverband code coverage
-rake coverband:clear         # reset Coverband coverage data, helpful for development, debugging, etc
+```ruby
+Rails.application.routes.draw do
+  mount Coverband::Reporters::Web.new, at: '/coverage'
+end
 ```
 
-You can view the report different ways, but the easiest is the Rake task which opens the SimpleCov formatted HTML.
-
-`rake coverband:coverage`
-
-This should auto-open in your browser, but if it doesn't the output file should be in `coverage/index.html`
+But don't forget to _protect your source code with proper authentication_. Something like this when using devise:
 
-## Viewing the Report in App
-
-First setup Coverband to [write reports to S3](#writing-coverband-results-to-s3) you can host the S3 file with a built in rack app in Coverband. Just configure your Rails route `config/routes.rb`
-
-```
+```ruby
 Rails.application.routes.draw do
-  # ... lots of routes
-  mount Coverband::Reporters::Web.new, at: '/coverage'
+  authenticate :user, lambda { |u| u.admin? } do
+    mount Coverband::Reporters::Web.new, at: '/coverage'
+  end
 end
 ```
 
-__NOTE__: ADD PASSWORD PROTECTION OR YOU CAN EXPOSE ALL YOUR SOURCE CODE
+### Coverband Web Endpoint
 
-It is easy to add basic protection around the coverage data, below shows how you can use devise or basic auth, by adding a bit of code to your `config/routes.rb` file.
+The web endpoint is a barebones endpoint that you can either expose direct (after authentication) or you can just link to the actions you wish to expose. The index is intended as a example to showcase all the features.
 
-```
-# protect with existing Rails devise configuration
-devise_constraint = lambda do |request|
-  request.env['warden'] && request.env['warden'].authenticate? && request.env['warden'].user.admin?
-end
+![image](https://raw.github.com/danmayer/coverband/master/docs/coverband_web_update.png)
 
-# protect with http basic auth
-# curl --user foo:bar http://localhost:3000/coverage
-Rails.application.routes.draw do
-  # ... lots of routes
+> The web index as available on the Coverband Demo site
 
-  # Create a Rack wrapper around the Coverband Web Reporter to support & prompt the user for basic authentication.
-  AuthenticatedCoverband = Rack::Builder.new do 
-    use Rack::Auth::Basic do |username, password|
-      username == 'foo' && password == 'bar'
-    end
+- **force coverage collection:** This triggers coverage collection on the current webserver process
+- **reload Coverband files:** This has Coverband reload files as configured (force reload of some files that might not capture Coverage on boot). This can be used to reload files on demand.
+- **clear coverage report:** This will clear the coverage data. This wipes out all collected data (**dangerous**)
 
-    run Coverband::Reporters::Web.new 
-  end
+### Rake Tasks
 
-  # Connect the wrapper app to your desired endpoint.
-  mount AuthenticatedCoverband, at: '/coverage'
-end
-```
+The rake task generates a report locally and opens a browser pointing to `coverage/index.html`.
 
-# Verify Correct Installation
+`rake coverband:coverage`
 
-* boot up your application
-* run app and hit a controller (via a web request, at least one request must complete)
-* run `rake coverband:coverage` this will show app initialization coverage
-* make another request, or enough that your reporting frequency will trigger
-* run `rake coverband:coverage` and you should see coverage increasing for the endpoints you hit.
+This is mostly useful in your local development environment.
 
-# Coverband Demo
+##### Example Output
 
-Take Coverband for a spin on the live Heroku deployed [Coverband Demo](https://coverband-demo.herokuapp.com/). The [full source code for the demo](https://github.com/danmayer/coverband_demo) is available to help with installation, configuration, and understanding of basic usage.
-
-# How To Use
+Since Coverband is [Simplecov](https://github.com/colszowka/simplecov) output compatible it should work with any of the `SimpleCov::Formatter`'s available. The output below is produced using the default Simplecov HTML formatter.
 
-Below is my Coverband workflow, which hopefully will help other best use this library.
+Index Page
+![image](https://raw.github.com/danmayer/coverband/master/docs/coverband_index.png)
 
-* <a href="#installation">Install Coverband</a>
-* Start your app and hit a few endpoints
-* Validate data collection and code coverage with  `rake coverband:coverage`
-* If you see app startup and recent visits showing, setup is correct
-* I generally configure the mountable web endpoint to [view the data via the web-app](https://github.com/danmayer/coverband#viewing--hosting-s3-coverband-results-in-app)
-* After Coverband has been verified to be working on production, I let it run for a few weeks.
-* Then I view the report and start submitting PRs for the team to review delete large related sets of code that no longer are in use.
+Details on an example Sinatra app
+![image](https://raw.github.com/danmayer/coverband/master/docs/coverband_details.png)
 
-### Coverband Web Endpoint
+# Verify Correct Installation
 
-The web endpoint is a barebones endpoint that you can either expose direct (after authentication) or you can just link to the actions you wish to expose. The index is intended as a example to showcase all the features.
+- boot up your application
+- run app and hit a controller (via a web request, at least one request must complete)
+- run `rake coverband:coverage` this will show app initialization coverage
+- make another request, or enough that your reporting frequency will trigger
+- run `rake coverband:coverage` and you should see coverage increasing for the endpoints you hit.
 
-![image](https://raw.github.com/danmayer/coverband/master/docs/coverband_web.png)
-> The web index as available on the Coverband Demo site
+# Coverband Demo
 
-* __collect data, update report, & view:__ This does everything need to view up to date Coverage 
-   * it triggers a coverage collection on the current webserver process
-   * it generates a new html coverage report and pushes it to S3
-   * it then loads that report for you to view
-* __view coverage report:__ Don't need to update the data just view the current report
-* __update coverage data (collect coverage):__ This triggers coverage collection on the current webserver process
-* __update coverage report (rebuild report):__ This will rebuild the HTML report from the latest available data
-* __clear coverage report:__ This will clear the coverage data. This wipes out all collected data (__dangerous__)
-* __reload Coverband files:__ This has Coverband reload files as configured (force reload of some files that might not capture Coverage on boot)
+Take Coverband for a spin on the live Heroku deployed [Coverband Demo](https://coverband-demo.herokuapp.com/). The [full source code for the demo](https://github.com/danmayer/coverband_demo) is available to help with installation, configuration, and understanding of basic usage.
 
 ### Example apps
 
-- [Rails 5.2.x App](https://github.com/danmayer/coverage_demo)
+- [Rails 5.2.x App](https://github.com/danmayer/coverband_demo)
 - [Sinatra app](https://github.com/danmayer/churn-site)
 - [Non Rack Ruby app](https://github.com/danmayer/coverband_examples)
 
-### Example Output
-
-Since Coverband is [Simplecov](https://github.com/colszowka/simplecov) output compatible it should work with any of the `SimpleCov::Formatter`'s available. The output below is produced using the default Simplecov HTML formatter.
-
-Index Page
-![image](https://raw.github.com/danmayer/coverband/master/docs/coverband_index.png)
-
-Details on a example Sinatra app
-![image](https://raw.github.com/danmayer/coverband/master/docs/coverband_details.png)
-
-### Advanced Coverband Config
+# Advanced Config
 
-You may need to configure Coverband you can either do that passing in all configuration options to `Coverband.configure` in block format, or a simpler style is to call `Coverband.configure` with no params which will load `config/coverband.rb` expecting it to configure the app correctly.
+If you need to configure coverband, this can be done by creating a `config/coverband.rb` file relative to your project root.
 
-* See [lib/coverband/configuration.rb](https://github.com/danmayer/coverband/blob/master/lib/coverband/configuration.rb) for all options
-* I strongly recommend setting up the S3 report adapter, which can't be automatically configured
-* By default Coverband will try to stored data to Redis
-	* Redis endpoint is looked for in this order: `ENV['COVERBAND_REDIS_URL']`, `ENV['REDIS_URL']`, or `localhost`
+- See [lib/coverband/configuration.rb](https://github.com/danmayer/coverband/blob/master/lib/coverband/configuration.rb) for all options
+- By default Coverband will try to stored data to Redis \* Redis endpoint is looked for in this order: `ENV['COVERBAND_REDIS_URL']`, `ENV['REDIS_URL']`, or `localhost`
 
- Below is an example config file for a Rails 5 app:
+Below is an example config file for a Rails 5 app:
 
 ```ruby
 #config/coverband.rb
 Coverband.configure do |config|
+  config.store = Coverband::Adapters::RedisStore.new(Redis.new(url: ENV['MY_REDIS_URL']))
+  config.logger = Rails.logger
   # configure S3 integration
   config.s3_bucket = 'coverband-demo'
   config.s3_region = 'us-east-1'
@@ -205,6 +164,20 @@ Coverband.configure do |config|
 end
 ```
 
+### Ignoring Files
+
+Sometimes you have files that are known to be valuable perhaps in other environments or something that is just run very infrequently. Opposed to having to mentally filter them out of the report, you can just have them ignored in the Coverband reporting by using `config.ignore` as shown below. Ignore takes a string but can also match with regex rules see how below ignores all rake tasks as an example.
+
+```
+config.ignore +=  ['config/application.rb',
+                   'config/boot.rb',
+                   'config/puma.rb',
+                   'config/schedule.rb',
+                   'bin/*'
+                   'config/environments/*',
+                   'lib/tasks/*']
+```
+
 ### Writing Coverband Results to S3
 
 If you add some additional Coverband configuration your coverage html report will be written directly to S3, update `config/coverband.rb` like below.
@@ -226,9 +199,17 @@ ENV['AWS_ACCESS_KEY_ID']
 ENV['AWS_SECRET_ACCESS_KEY']
 ```
 
+### Coverage Data Migration
+
+Between the release of 4.0 and 4.1 our data format changed. This resets all your coverage data. If you want to restore your previous coverage data, feel free to migrate.
+
+`rake coverband:migrate`
+
+- We will be working to support migrations going forward, when possible
+
 ### Clear Coverage
 
-Now that Coverband uses MD5 hashes there should be no reason to manually clear coverage unless one is testing, changing versions, possibly debugging Coberband itself.
+Now that Coverband uses MD5 hashes there should be no reason to manually clear coverage unless one is testing, changing versions, possibly debugging Coverband itself.
 
 `rake coverband:clear`
 
@@ -254,9 +235,9 @@ rake coverband:coverage      # report runtime coverband code coverage
 
 ### Forcing Coverband to Track Coverage on files loaded during boot `safe_reload_files`
 
-The way Coverband is built it will record and report code usage in production for anything `required` or `loaded` after calling `Coverband.start`. This means some of Rails initial files and Gems are loaded before you can generally call `Coverband.start` for example if you use the `application.rb` to initialize and start Coverband, that file will be reported as having no coverage, as it can't possibly start Coverband before the file is loaded. 
+Coverband will report code usage for anything `required` or `loaded` after calling `Coverband.start` which happens automatically when coverband is required. This means some of the files loaded before coverband such as the Rails application.rb will be reported as having no coverage.
 
-The `safe_reload_files` reload option in the configuration options can help to ensure you can track any files you want regardless of them loading before Coverband. For example if I wanted to show the coverage of `config/coverband.rb` which has to be loaded before calling `Coverband.start` I could do that by adding that path to the `safe_reload_files` option.
+The `safe_reload_files` reload option in the configuration options can help to ensure you can track any files regardless of loading before Coverband. For example if I wanted to show the coverage of `config/coverband.rb`, which has to be loaded before calling `Coverband.start`, I could do that by adding that path to the `safe_reload_files` option.
 
 ```
 Coverband.configure do |config|
@@ -265,21 +246,44 @@ Coverband.configure do |config|
   config.safe_reload_files = ['config/coverband.rb']
 end
 ```
-By adding any files above you will get reporting on those files as part of your coverage runtime report.
 
+By adding any files above you will get reporting on those files as part of your coverage runtime report. The files are reloaded when Coverband first starts, you can also trigger a reload via the web interface.
 
 ### Collecting Gem / Library Usage
 
-By default Coverband has assumed you are trying to track your application code usage not all the supporting framework and library (Gems) code usage. There has been some good points and reasons folks want to track library usage, for example to find out which Gems they aren't actually using in production. See some of the discussion on [issue 21](https://github.com/danmayer/coverband/issues/21).
+Gem usage can be tracked by enabling the `track_gems` config.
 
-How to collect gem usage with Coverband:
+```
+Coverband.configure do |config|
+  config.track_gems = true
+end
+```
+
+The `track_gems` feature exposes a Gems tab in the report which prints out the percentage usage of each Gem. See demo [here](https://coverband-demo.herokuapp.com/coverage?#_Gems).
 
-* use the `safe_reload_files` feature to add the path of all gem files you wish to track
-* --- or ---
-* ensure you call `require 'coverband'` which triggers `Coverband.start` before loading all your gems
-   * while possible this is currently hard as Rails and most environments load your whole Gemfile
-   * we are looking for an improve and easier way to support this.
+When tracking gems, it is important that `Coverband#start` is called before the gems to be tracked are required. Since `Coverband#start` is automatically called by default when coverband is required, list coverband before the other gems to be tracked within your Gemfile. The exception to this are gems like rails and resque. Since coverband has some specific intergrations for these frameworks, these two gems should be required first.
 
+The track_gems config only exposes the overall usage of a gem. In order to see the detail of each file, enable the `gem_details` flag.
+
+```
+Coverband.configure do |config|
+  config.track_gems = true
+  config.gem_details = true
+end
+```
+
+This flag exposes line by line usage of gem files. Unfortunately due to the way the coverband report is currently rendered, enabling `gem_details` slows down viewing of the coverage report in the browser and is not yet recommended.
+
+### Manually Starting Coverband
+
+Coverband starts on require of the the library which is usually done within the Gemfile. This can be disabled by setting the `COVERBAND_DISABLE_AUTO_START` environment variable. This environment variable can be useful to toggle coverband on and off in certain environments.
+
+In order to start coverband manually yourself when this flag is enabled, call `Coverband.configure` followed by `Coverband.start`.
+
+```ruby
+Coverband.configure
+Coverband.start
+```
 
 ### Verbose Debug / Development Mode
 
@@ -305,35 +309,10 @@ If you are trying to debug locally wondering what code is being run during a req
       ...
      [517, 1617], [516, 38577]]
 
-
-### Conflicting .Simplecov: Issue with Missing or 0% Coverage Report
-
-If you use SimpleCov to generate code coverage for your tests. You might have setup a `.simplecov` file to help control and focus it's output. Often the settings you want for your test's code coverage report are different than what you want Coverband to be reporting on. Since Coverband uses the SimpleCov HTML formatter to prepare it's report.
-
-So if you had something like this in a `.simplecov` file in the root of your project, as reported in [issue 83](https://github.com/danmayer/coverband/issues/83)
-
-```
-require 'simplecov'
-
-SimpleCov.start do
-  add_filter 'app/admin'
-  add_filter '/spec/'
-  add_filter '/config/'
-  add_filter '/vendor/'
-  add_filter 'userevents'
-end
-```
-
-You could see some confusing results... To avoid this issue Coverband has a Rake task that will ignore all Simplecov filters.
-
-`rake coverband:coverage_no_filters`
-
-This will build the report after disabling any `.simplecov` applied settings.
-
 # Prerequisites
 
-* Coverband 3.0.X+ requires Ruby 2.3+
-* Coverband currently requires Redis for production usage
+- Coverband 3.0.X+ requires Ruby 2.3+
+- Coverband currently requires Redis for production usage
 
 # Contributing To Coverband
 
@@ -350,19 +329,18 @@ If you are working on adding features, PRs, or bugfixes to Coverband this sectio
 
 If you submit a change please make sure the tests and benchmarks are passing.
 
-* run tests: 
-   * `bundle exec rake` 
-   * `BUNDLE_GEMFILE=Gemfile.rails4 bundle exec rake` (Same tests using rails 4 instead of 5)
-* view test coverage: `open coverage/index.html`
-* run the benchmarks before and after your change to see impact
-   * `rake benchmarks` 
+- run tests:
+  - `bundle exec rake`
+  - `BUNDLE_GEMFILE=Gemfile.rails4 bundle exec rake` (Same tests using rails 4 instead of 5)
+- view test coverage: `open coverage/index.html`
+- run the benchmarks before and after your change to see impact
+  - `rake benchmarks`
 
 ### Known Issues
 
-* __total fail__ on front end code, because of the precompiled template step basically coverage doesn't work well for `erb`, `slim`, and the like.
-  * related it will try to report something, but the line numbers reported for `ERB` files are often off and aren't considered useful. I recommend filtering out .erb using the `config.ignore` option. The default configuration excludes these files
-* If you have SimpleCov filters, you need to clear them prior to generating your coverage report. As the filters will be applied to Coverband as well and can often filter out everything we are recording.
-* coverage doesn't show for Rails `config/application.rb` or `config/boot.rb` as they get loaded when loading the Rake environment prior to starting the `Coverage` library.
+- **total fail** on front end code, because of the precompiled template step basically coverage doesn't work well for `erb`, `slim`, and the like.
+  - related it will try to report something, but the line numbers reported for `ERB` files are often off and aren't considered useful. I recommend filtering out .erb using the `config.ignore` option. The default configuration excludes these files
+- coverage doesn't show for Rails `config/application.rb` or `config/boot.rb` as they get loaded when loading the Rake environment prior to starting the `Coverage` library. See [reload files section](#forcing-coverband-to-track-coverage-on-files-loaded-during-boot-safe_reload_files).
 
 ### Debugging Redis Store
 

data/Rakefile

@@ -13,7 +13,7 @@ Rake::TestTask.new(:test) do |test|
   # exclude benchmark from the tests as the way it functions resets code coverage during executions
   # test.pattern = 'test/unit/*_test.rb'
   # using test files opposed to pattern as it outputs which files are run
-  test.test_files = FileList['test/unit/**/*_test.rb']
+  test.test_files = FileList['test/integration/**/*_test.rb', 'test/coverband/**/*_test.rb']
   test.verbose = true
 end
 

data/changes.md

@@ -24,7 +24,6 @@ Will be the fully modern release that drops maintenance legacy support in favor
   - add coverage timerange support
 - Drop Simplecov dependency
 - improved web reporting
-  - no longer relying directly on HTML in S3 but dynamically generated from any adapter
   - lists current config options
   - eventually allow updating remote config
   - full theming
@@ -32,12 +31,22 @@ Will be the fully modern release that drops maintenance legacy support in favor
 - additional adapters: Memcache, S3, and ActiveRecord
 - add articles / podcasts like prontos readme https://github.com/prontolabs/pronto
 - Add detailed Gem usage report, if we collect and send gem usage we can give percentage of gem code used, which should help application developers know when to remove gem dependencies (0%) or perhaps inline single methods for little usage (using <= 5%) for example.
-- add additional config / protection options on Coverage clear
 - add meta data information first seen last recorded to the coverage report views (probably need to drop simplecov for that).
   - more details in this issue: https://github.com/danmayer/coverband/issues/118
 - Make good video on setup, install, usage
 - See if we can add support for views / templates
-  - using this technique https://github.com/ioquatix/covered 	
+  - using this technique https://github.com/ioquatix/covered
+- Better default grouping (could use groups features for gems for rails controllers, models, lib, etc)
+- Improved logging for easier debugging and development
+  - drop the verbose mode and better support standard logger levels
+- Possibly setup a build assets system
+  - my JS rules expanded the compressed JS at the top of application.js, basically we want to stitch together JS
+  - I guess we could also load multiple JS files as most of the JS is just default compressed JS and a tiny amount of actual app JS.
+- lazy load for Coverband results
+- view layer file coverage
+- move all code to work with relative paths leaving only stdlib Coverage working on full paths
+- add gem_safe_lists to track only some gems
+- add gem_details_safe list to report on details on some gems
 
 ### Coverband_jam_session
 
@@ -64,12 +73,54 @@ Feature Ideas:
 
 # Alpha
 
-### Coverband 4.0.2.alpha
+### Coverband 4.3.0?
 
+- further improvements on eager_loading detection
 - ?
 
 # Released
 
+### Coverband 4.2.0
+
+**NOTE:** This release introduces load time and runtime Coverage. To get the full benifit of this feature you need to reset you coverage data (`rake coverband:clear` or clear via the web UI). Until you clear the combined result is still correct, but your runtime data will be mixed with previous data. This is due to an additive change in how we store coverage. We didn't reset by default as the coverage history for some folks may be more important than runtime breakdown.
+
+- loadtime vs runtime coverage
+  - This fixes the coverage last seen date to exclude just load time data
+  - now you can see boot time coverage vs code hit during production execution
+  - list view shows runtime percentage and runtime hits
+  - file view shows line hits load, runtime, and combined
+- perf speedup on gem details views
+- ajax load code views for more responsive pages on large projects
+- fix for issues with COVERBAND_DISABLE_AUTO_START
+- silence warnings
+- move from thread based reporter instance to process based instance
+- thanks Karl Baum for much of the above mentioned work
+- clear coverage on individual files
+- we have a logo, thanks Dave Woodall
+
+### Coverband 4.1.1
+
+- fix bug on info page when using namespaces
+- fix bug related to forking Ruby processes (Resque for example)
+  - bug caused negative line hits
+  - bug seemed to cause memory leaks (not entirely sure how)
+- various test improvements
+- fix bad requests on coverband web admin to `/coverage/favicon.png`
+- improved documentation
+
+### Coverband 4.1.0
+
+- default disabled web clear, add config option to allow it
+- out of the box support for resque
+- readme improvements
+- fix on regression of merging directory changing deployments
+  - fixes for duplicate root paths
+- pilot release of Gems tracking (disabled by default) - todos - support multiple gem paths (various version managers setup multiple gem paths) - speed up page load by allowing multiple pages
+- added web settings and debug views
+  - added support for seeing coverage data size consumed in redis
+- support coverage data migrations from 4.0.x to 4.1.0
+- fixes for heroku /tmp asset building
+
 ### Coverband 4.0.1
 
 - drops Simplecov runtime dependency
@@ -78,7 +129,7 @@ Feature Ideas:
 - reduced the S3 dependencies to minimal set (not loading all of aws-sdk, only aws-sdk-s3), ensured they are optional
 - Improved Coverband web admin
 - Coverage reports include timestamps of Coverage collection
-- Added Coveralls to the dev process thanks @dondonz 
+- Added Coveralls to the dev process thanks @dondonz
 - now tested under Ruby 2.6.0 thanks @Kbaum
 - improved full stack testing for Rails 5 & 4
 - warning before clear coverage on coverband web

data/coverband.gemspec

@@ -24,7 +24,6 @@ Gem::Specification.new do |spec|
   # to test sdk 2 use this one
   spec.add_development_dependency 'aws-sdk-s3', '~> 1'
   spec.add_development_dependency 'benchmark-ips'
-  spec.add_development_dependency 'bundler', '~> 1.3'
   spec.add_development_dependency 'capybara'
   spec.add_development_dependency 'm'
   spec.add_development_dependency 'memory_profiler'
@@ -33,8 +32,9 @@ Gem::Specification.new do |spec|
   spec.add_development_dependency 'rack'
   spec.add_development_dependency 'rack-test'
   spec.add_development_dependency 'rake'
-  spec.add_development_dependency 'simplecov'
-
+  spec.add_development_dependency 'resque'
+  # temporarily needed to fun tests for classifier-reborn as part of benchmarks
+  spec.add_development_dependency 'minitest-reporters'
 
   # TODO: used for benchmarking and tests I think we have other better benchmarking
   # perhaps time to drop this and refactor.
@@ -44,6 +44,8 @@ Gem::Specification.new do |spec|
   # require 'byebug'; byebug
   spec.add_development_dependency 'pry-byebug'
 
+  spec.add_development_dependency 'minitest-profile'
+
   # TODO: Remove when other production adapters exist
   # because the default configuration of redis store, we really do require
   # redis now. I was reluctant to add this, but until we offer another production