Meta Bates » rcov

CoverMe – Code Coverage for Ruby 1.9 Reaches RC1

Mark Bates — Thu, 30 Sep 2010 16:09:25 +0000

In August I announced CoverMe a code coverage tool for Ruby 1.9. Well, today I announce that it has hit it’s first release candidate! I’ve very excited by the fact it’s getting close to an ‘official’ release.

The response to CoverMe has been great and through feedback from the community I’ve made a lot of improvements and fixed a lot of issues.

While quite a few things have changed under the hood, not much has changed in how you use CoverMe.

Installation

The following are instructions for how you would configure CoverMe for a Rails 3 project, adjust to your local environment accordingly.

In your Gemfile add the following:

gem 'cover_me', '>= 1.0.0.rc1', :group => :test

Then run:

$ bundle install

After CoverMe is installed place the following line at the VERY TOP of your ‘test_helper.rb’ or ‘spec_helper.rb’ file (for Cucumber put it at the top of the ‘env.rb’ file):

require 'cover_me'

I can’t emphasize enough how important it is that the require statement is at the VERY top of that file!

Finally (and optionally) run:

$ rails g cover_me:install

This will simply install a Rake task that will wrap both Test::Unit and RSpec tasks with CoverMe and will launch the results at the end of the test suites. I would recommend it. It’s kinda the whole point.

That’s it!

Enjoy the release candidate, and of course, please let me know if you find any issues with it. Issues can be reported on here.

CoverMe – Code Coverage for Ruby 1.9

Mark Bates — Fri, 13 Aug 2010 17:49:44 +0000

Ruby 1.9(.2) is an amazing language to develop applications in. It’s faster, more powerful, cleaner, and a huge improvement over Ruby 1.8.x. Because of those reasons every Ruby developer should move to this exciting new version of our language.

When making a move of this size it’s important to have the right tools to help us along. Unfortunately, one of the most useful tools as a Ruby developer, RCov, does not work with Ruby 1.9.

RCov, for those unfamiliar analyzes your code and tells you which part of your code was not executed. This is INCREDIBLY useful when hooked up to your test suite. While, it’s not the only metric you should use when determining how good your test coverage it, it certainly is a great first step to point out exactly which parts of your code haven’t been touched at all!

Enter CoverMe.

History

While working on a Ruby 1.9/Rails 3 project, and loving everything about it (except for the lack of RCov), I came across a post by Aaron Patterson (of Nokogiri fame). In this post he quickly outlined a very basic coverage tool using the new built-in Coverage module in Ruby 1.9.

After spending a morning playing with it, I was quickly able to grow the idea into something useful for the project. Later that day the company I was consulting for (BiddingForGood.com), and in particular their chief architect, Stuart Garner, told me to take a day or two and clean it up and release it for the world to use, and so here it is.

Features

Here is a brief overview of the features of CoverMe:

Index Page

Sortable column headers (File, Lines, Lines of Code, Tested %).
Searching/filtering by file name.
Filtering by coverage percent.
Color coded list of files to quickly see which ones are 100% covered, > 90% covered, or less than 90% covered.
Large color coded average coverage percent, for quick reference.

Detail Page

Line by line coverage report
Color coded lines to quickly see which lines where executed and which ones were not.
Side by side viewing with the corresponding test/spec file (if one exists).

See the README file for more information on installation and usage.

Thanks

I would just quickly like to give another quick thanks to Aaron Patterson for pointing out the Coverage module in Ruby 1.9 and inspiring this, hopefully, helpful little gem. Also another big thanks to Stuart Garner for pushing me to package this up and release it to the world.

Screenshots

Release 0.5.0

Mark Bates — Tue, 06 May 2008 18:33:47 +0000

I know I’ve been talking about this release for a while now, and here it finally is. There’s some good bug fixes in here, a few new rake tasks, and some other little things like that.

The biggest thing, however, is what’s been causing a stir online now for the past few days, I’ve split out the ORM support into separate gems. I’m not going to go over it again, you can find all the details here:Â http://www.mackframework.com/2008/05/04/orms-and-mack/

Needless to say this is a good release to get, if not for the bug fixes alone, but for the great db:create rake tasks that are now in there. Thanks, again, to Darsono Sutedja for his great contributions.

Changelog

Added rake db:create and db:create:all rake tasks.
Refactored out constants, such as MACK_ROOT and MACK_ENV and made them into Mack::Configuration.env, Mack::Configuration.root, etc…
Added test:stats and test:coverage Rake tasks.
Removed support for ActiveRecord and DataMapper and moved them into their own gems.
Fixed a bug where yields in ERB weren’t giving the desired results.
DataMapper database.yml file can now be nested, and is generated as such.
Cleaned up some tests, and refactored the HTML generation stuff.
Fixed a bug with the scaffold generating ‘bad’ methods instead of ‘post’
Made error_messages_for more compatible with DataMapper.
Fixed a bug loading url.rb and uploaded_file.rb found by Phil Darnowsky
[dsutedja] Render method (in controller_base) now accepts response status code.
gem: mack_ruby_core_extensions 0.1.23
gem: genosaurus 1.1.4
gem: datamapper 0.3.2
gem: rcov 0.8.1.2.0
gem: mack-data_mapper 0.5.0
gem: erubis 2.6.0