# Rspec + rcov + rails + sequel (false coverage report)

**URL:** <https://www.ruby-forum.com/t/rspec-rcov-rails-sequel-false-coverage-report/183644>\
**Category:** Rails\
**Created:** [February 18, 2010, 3:00am UTC](https://www.ruby-forum.com/t/rspec-rcov-rails-sequel-false-coverage-report/183644 "2010-02-18T03:00:08Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![destiney](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/f07891/32.png) [@destiney](https://www.ruby-forum.com/u/destiney)\
**Post date:** [February 18, 2010, 3:00am UTC](https://www.ruby-forum.com/t/rspec-rcov-rails-sequel-false-coverage-report/183644/1 "2010-02-18T03:00:08Z")

</div>

Anyone use rcov (0.9.4) on a rails (2.3.5) app that is using Sequel  
(3.8.0)? The coverage report is including blank and comment lines as  
not being executed. It is also including the class definition line  
as  
being not executed when the instance and class methods have been  
executed. I’m not sure if this has to really do with Sequel, because  
this is also happening to the controller specs. Rspec(1.3.0) was run  
with rake(0.8.7) like this rake spec:rcov. The report seems to be  
totally bogus based on blanks and comments being included. I have  
used these in the past with AR and it worked fine. I just can’t  
believe Sequel would cause these to break.

any ideas?

Thanks,

GregD