Fix Rcov #7
Comments
From my previous experiments last week, I've now gone for the "someone else must have seen it" approach. Turns out, it's fairly common for people to experience this issue with rcov when using rspec 2.0. Link: http://stackoverflow.com/questions/8886258/rcov-for-rspec-2-not-detecting-coverage-correctly-not-rails Sadly, most of the solutions provided tend to be along the lines of "upgrade to 1.9 and use simplecov". |
- Alphabetise dev deps - Directly use ~> 1.0.0 for rcov instead of calling it from under metric_fu
This still doesn't fix the rcov usage, but it at least shows better ouput, removing the gems coverage. Only showing the coverage for files in lib/ Also removed rcov from being one of the outputs for metric_fu
The Ruby Community's default answer is to upgrade. On Wed, Mar 7, 2012 at 12:44 PM, Kushal Pisavadia <
Julian Simpson |
nice work. Coverage didn't suffer too badly, either. |
Perhaps we bin metric_fu's bundled rcov, but coverage is good
The text was updated successfully, but these errors were encountered: