On Fri, Mar 11, 2011 at 2:55 PM, James OBrien wrote:
> I'm using Rake to run my specs e.g.
>
> task :test do
> Rake::Task['spec'].execute
> end
>
> how can I aspect this to include some sort of coverage report - RCov maybe?
>
> Of course, I could just escape to the command line with something l
I'm using Rake to run my specs e.g.
task :test do
Rake::Task['spec'].execute
end
how can I aspect this to include some sort of coverage report - RCov maybe?
Of course, I could just escape to the command line with something like
system('rcov rspec ') but I prefer to solve this
programaticaly si
It looks like it can't find Rcov... do you have rcov installed? can
you rcov --help from a command line?
Thanks
Jay
On Wed, Apr 28, 2010 at 11:10 PM, Patrick J. Collins
wrote:
> I followed the instructions in the rspec book to setup rcov. I appened to
> the end of my RAILS_ROOT/Rakefile:
> re
I followed the instructions in the rspec book to setup rcov. I appened to the
end of my RAILS_ROOT/Rakefile:
require 'rake'
require 'spec/rake/spectask'
namespace :spec do
desc "Run specs with RCov"
Spec::Rake::SpecTask.new('rcov') do |t|
t.spec_files = FileList['spec/**/
I solved it with relevance-rcov (formerly spicycode-rcov).
There were remnants of an the failed "gem install rcov" attempt that
caused errors. Some sudo rm -rf ... fixed that.
Seemes to work fine on a test project.
Tick
--
Posted via http://www.ruby-forum.com/.
_
Has anyone got RCov working with Ruby 1.9.1? The rcov gem won't even
install, and the spicycode-rcov gem crashes.
It would be nice to still benefit from rcovs features.
Tick
--
Posted via http://www.ruby-forum.com/.
___
rspec-users mailing list
rspec-us
James Byrne wrote:
> I think that I have this straightened now.
> Cucumber::Rake::Task.new(:cucumber) etc. are factory methods that are
> processed as encountered by rake.
Having spent the day delving into Rake and the internals of factory
methods for Rake included with RSpec and Cucumber, I d
James Byrne wrote:
> I am having a good deal of trouble grappling with how rake tasks are
> processed. In my rcov.rake file I have this:
I think that I have this straightened now.
Cucumber::Rake::Task.new(:cucumber) etc. are factory methods that are
processed as encountered by rake.
--
Poste
I am having a good deal of trouble grappling with how rake tasks are
processed. In my rcov.rake file I have this:
desc "Rcov code coverage reports"
require 'rcov/rcovtask'
require 'spec/rake/spectask'
require 'cucumber/rake/task'
#task :rcov => "rcov:complete"
namespace :rcov do
...
Cuc
I am trying to get a customized rcov rake task working. What I have so
far looks like this:
desc "Rcov code coverage reports"
require 'rcov/rcovtask'
require 'spec/rake/spectask'
require 'cucumber/rake/task'
task :rcov => "rcov:all"
namespace :rcov do
Rcov::RcovTask.new(:all) do
task
desc "Rcov code coverage reports"
task :rcov => "rcov:all"
require 'rcov/rcovtask'
namespace :rcov do
Rcov::RcovTask.new(:all) do
task :rcov => "rcov:testunit"
end
Rcov::RcovTask.new(:testunit) do |t|
t.libs << "test"
t.output_dir = 'coverage'
t.test_files = FileList['test/
OS = MS-WinXPproSP3 / CYGWIN_NT-5.1 1.5.25(0.156/4/2) 2008-06-12 19:34
ruby 1.8.7 (2008-08-11 patchlevel 72) [i386-cygwin]
rails (2.2.2)
rake (0.8.3)
rcov (0.8.1.1.0)
I am trying to develop a rake task that will aggregate the results for
testunit, spec and cucumber tests. However, I find that I c
Thankyou Chad and Aslak, those patches seem to have worked perfectly
- time to apply the threshold crank! [rubs hands gleefully]
On 13 Sep 2008, at 16:50, Chad Humphries wrote:
I've got a version of rcov up at github (sudo gem install
spicycode-rcov --source=http://gems.github.com/) incorpora
On Sat, Sep 13, 2008 at 12:36 PM, Matt Wynne <[EMAIL PROTECTED]> wrote:
> Hi all,
> I appreciate that this is not an RSpec question, but I wondered if anyone
> out there can offer some pointers. We're using the latest versions of RSpec
> and RCov, and ruby --version says this (on the Ubuntu build s
I've got a version of rcov up at github (sudo gem install
spicycode-rcov --source=http://gems.github.com/) incorporating many of
the fixes for rcov segfaults. So far none of the old standard
crashes have crept back up. Give it a try and let me know how it
works for you.
--
Chad
On Sat, Sep 13,
Hi all,
I appreciate that this is not an RSpec question, but I wondered if
anyone out there can offer some pointers. We're using the latest
versions of RSpec and RCov, and ruby --version says this (on the
Ubuntu build server):
ruby 1.8.6 (2008-07-17 patchlevel 279) [x86_64-linux]
On Jun 7, 2008, at 1:11 PM, Maurício Linhares wrote:
Hello again :)
I'm trying to run rcov on my specs here but i'm getting a lot of
segmentation faults (and they usually happen at different places):
/home/mauricio/NetBeansProjects/reeds/vendor/rails/activerecord/lib/
active_record/attribute
On Jun 7, 2008, at 12:11 PM, Maurício Linhares wrote:
Hello again :)
I'm trying to run rcov on my specs here but i'm getting a lot of
segmentation faults (and they usually happen at different places):
/home/mauricio/NetBeansProjects/reeds/vendor/rails/activerecord/lib/
active_record/attribute
Hello again :)
I'm trying to run rcov on my specs here but i'm getting a lot of
segmentation faults (and they usually happen at different places):
/home/mauricio/NetBeansProjects/reeds/vendor/rails/activerecord/lib/active_record/attribute_methods.rb:211:
[BUG] Segmentation fault ruby 1.8.6 (2007-
On 9/25/07, Brandon Keepers <[EMAIL PROTECTED]> wrote:
> When I run spec:rcov on my continuous integration server, the rcov
> report is including many other libraries in the report, including
> some from standard lib and gems. Has anyone else had this problem or
> have any ideas for how to limit i
On 9/24/07, Brandon Keepers <[EMAIL PROTECTED]> wrote:
> When I run spec:rcov on my continuous integration server, the rcov
> report is including many other libraries in the report, including
> some from standard lib and gems. Has anyone else had this problem or
> have any ideas for how to limit i
When I run spec:rcov on my continuous integration server, the rcov
report is including many other libraries in the report, including
some from standard lib and gems. Has anyone else had this problem or
have any ideas for how to limit it just to coverage of code in app/
and lib/?
Thanks,
When I run spec:rcov on my continuous integration server, the rcov
report is including many other libraries in the report, including
some from standard lib and gems. Has anyone else had this problem or
have any ideas for how to limit it just to coverage of code in app/
and lib/?
Thanks,
23 matches
Mail list logo
