According to their documentation, Coverband is:
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. (…) 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
Coverband gives you insights into what code is being loaded in your Rails application, which you can also think of as code that is being used by the application. This can be a very useful tool for refactoring, and removing code that is no longer used or needed.
The rest of the tutorial will assume you already have a functioning Rails app!
Add the Coverband gem to your
Gemfile. I personally decided to keep it in my development group, because I didn’t see any value in having the dashboard available in production.
# Gemfile gem "coverband", group: :development # or group :development do gem "coverband" end
Coverband stores coverage data in Redis. According to the documentation, the Redis endpoint is looked for in this order:
ENV['COVERBAND_REDIS_URL'] ENV['REDIS_URL'] localhost
You can also specifically set this in a Coverband initializer file. If you are using the template that I’m using then you should be all set, otherwise make sure you are running Redis locally, bundle the
redis gem, and your app can access it.
Let’s configure the gem. Create an initializer file for Coverband, which should look like the following:
# config/coverband.rb Coverband.configure do |config| config.ignore += ["config/application.rb", "config/boot.rb", "config/puma.rb", "bin/*", "config/environments/*", "lib/tasks/*",] end
These settings just tell Coverband to ignore our specified files and paths.
Now, lets add a route for coverband so we can view the web dashboard:
# config/routes.rb Rails.application.routes.draw do mount Coverband::Reporters::Web.new, at: "/coverband" if Rails.env.development? end
It is worth noting that if you are running this tool in production, you should protect this route with proper authentication.
We should be all set to see what Coverband can provide us!
Fire up the Rails server and navigate to
Alternatively, you can run the following Rake task and static files will be created in
coverage/. I would recommend making sure this directory is added to your
You should now be seeing is Coverband’s mountable web interface to easily view Coverband reports.
If we click on a file with 0% coverage, you will see the following message:
This file was never loaded during app runtime or loading (or was loaded before Coverband loaded)!
Basically this mean the code inside the file has not been loaded, and therefore not used.
If we click on a file with partial coverage, you should see something like:
This view will highlight the lines that have been used, and those that haven’t. Take care before you start ripping out code though, it’s possible that you just haven’t exercised that code yet.
posts_controller file in my example above, the code inside our
create methods is not being used. I am going to open up the UI, and create a new post. You will notice that the coverage report looks a little different now:
It is important to exercise some due diligence before removing code that Coverband flags. In the example above, after some investigation I realized I in fact do not need
config/spring.rb because I am not using
spring in this project. This is the power of this library, the ability to point you towards areas in your codebase that may be safe to remove; however, if I had removed the flagged code in the
posts_controller then I would be in some trouble.
It is also possible to use Coverband to track gem usage. This is still in experimental stages and not recommended for production according to the docs.
To see it in action, first let’s update our initializer:
# config/initializers/coverband.rb Coverband.configure do |config| config.track_gems = true config.ignore += ["config/application.rb", "config/boot.rb", "config/puma.rb", "bin/*", "config/environments/*", "lib/tasks/*",] end
According to the docs:
When tracking gems, it is important that Coverband#start is called before the gems to be tracked are required. The best way to do this is to require coverband before Bundle.require is called
So lets update
application.rb to make sure coverband is loaded before
Bundler.require is called:
# config/application.rb require "coverband" Bundler.require(*Rails.groups)
Restart the Rails server and you should now have a gem tab if you navigate back to
This can help give you insight into gems that may be safe to remove.
There is a config option to watch your views, but it was not working for me on
Rails 220.127.116.11 and
Ruby 2.7 so I won’t go into it now.
See the advanced configuration documentation for more information.
Coverband is a great tool to help you find code in your Rails app that may be safe to remove. The tool is not perfect though, so take care that the code can actually be safely removed. I personally used this tool on CodeFund’s codebase and found some code that could be removed! And who doesn’t like deleting code? Definitely recommend adding this tool to your tool belt.
Happy Coding!View All Articles