broken, I guess?

[ghost]

I did gem install cover_me, no errors. I see the gem listed when I run gem list.

I added require 'cover_me' to the TOP of my test_helper.rb.

I ran rails g cover_me:install. I noticed a new file, lib/tasks/cover_me.rake:

namespace :cover_me do
task :report do
require 'cover_me'
CoverMe.complete!
end
end
task :test do
Rake::Task['cover_me:report'].invoke
end
task :spec do
Rake::Task['cover_me:report'].invoke
end

Problems:

1. When I run rake -T I do not see any "cover_me" tasks.

2. When I run rake cover_me:report, I get:

Couldn't get a file descriptor referring to the console

3. When I Google "cover_me Couldn't get a file descriptor referring to the console" I get nothing helpful.

[bdwong]

I ran into this as well. I think these can be considered example rake tasks for rails code coverage. Try running rake spec or rake test and the default coverage directory will be created.

[kkdoo]

Same on ubuntu 10.10 with ruby 1.9.2-head and rails 3. Any fix?

[ghost]

The fix for me was to use simplecov:

https://github.com/colszowka/simplecov

It's really nice.

[functionreturnfunction]

If this helps anyone, this is looking like an Ubuntu issue. My development virtual machine runs 10.04, and I'm able to get a coverage report thusly:

~/my/rails/project$ sudo ~/.rvm/bin/rake test

This led me to the discovery that /dev/console is readable/writable by root and no one else. On a whim I made it world-readable (sudo chmod +r /dev/console), and the new error I get is:

openvt: Unable to open /dev/tty8: Permission denied

So the answer is buried somewhere in the specific way the Ubuntu handles consoles/ttys/security. I'll post more here if I find anything else out.