similar to: Extra Options to Heckle

Hi, I''m trying out RSpec with the heckle option (for mutation testing). Problem is that heckle goes into an infinite loop when running it on an example. I want to send a "--verbose" to heckle but can''t find a way to do that through the spec binary. Since this is not an uncommon situation when using heckle I would like this to be supported in some way by RSpec.

Hey list, Does anything exist that can show me which lines are explicitly tested? RCov is great, but it doesn''t really give a sense of _actual_ coverage, indeed, there is no guarantee that functions executed were in fact called as the result of a line being tested. I know nothing of the rspec internals, but would a simple list of executed lines be a relatively simple feature to add?

I''m working on tool to automatically run code metrics in the same way as autotest. It''s runs rcov, flog, and saikuro right now, and works with rspec and rails. It''s hosted at rubyforge: http://rubyforge.org/projects/autometric/ I''ve got a post on how to configure it with growl: http://benburkert.com/2007/11/9/introducing-autometric I''m hoping

I''ve created a short patch so that spec.opts can use a single line (or multiple lines for backwards compatibility) for options. I''ve run the specs against spec:trunk I have two questions: 1. I''ve run rake pre_commit, but after the specs are done running, I get this error: rake aborted! ERROR while running webgen: /opt/local/lib/ruby/site_ruby/1.8/

If I got this to work, do you think we could/should check in rspec_autotest into rspec? I''ve updated rspec_autotest abit, so let me know if you''d like the modified code. Scott

Hey list, RSpec is great, I''ve been using it at work for a couple of months now. One gripe I have is that I find it hard to know exactly to what extent my code is covered by the specs. I am aware of RCov and Heckle; they''re great, but I''d like to demonstrate another perspective of coverage analysis I''ve hacked up. The perspective is that of what is mocked and

Hi I can''t get heckle working. In fact, I''ve built an example so simple that it either shows a bug, or I am being really, REALLY stupid. Heckle does not appear to support RSpec directly, so I''m trying to use spec --heckle (RSpec trunk as of 10 mins ago, Heckle 1.4.1). I''ve constructed this pair of sample files: 18> ~/Desktop/heckle_test % cat

Running rails 1.2.3, rcov (0.8.0.2), rspec trunk (2865) - When running rake spec:rcov, I''m getting the following: Finished in 245.717813 seconds 856 examples, 0 failures, 48 pending /usr/local/lib/ruby/1.8/rexml/text.rb:292:in `normalize'': private method `gsub'' called for 0:Fixnum (NoMethodError) from /usr/local/lib/ruby/1.8/rexml/element.rb:1084:in

I svn up''ed this morning, to get the following message with rake spec: /Users/smt/src/web/urbis/trunk/vendor/plugins/rspec/lib/spec/example/ example_group_methods.rb:96:in `it'': Duplicate example: ''should contain the total number of messages'' (RuntimeError) Anyone have any ideas why this might be going on? My specs were all passing last night. Let me

I have something like the following: def my_fun my_fun2 do raise Error end end I know that I can verify that the method receives my_fun2. How can I mock/stub out the example to verify that it calls raise Error? Scott

Hi there I just started my first Merb app and I''m running into some weird things in Specs. When I do: describe "create action" do it "should create a new project" do project_params = {:name => ''bekkunin''} Project.should_receive(:create).with(project_params) controller, action = post(''/projects'', :project

Hi, I am using JRuby (trunk) and wrote a bunch of specifications for my code. Everything works fine so far. Now I am trying to integrate RCov in my test run. I have installed RCov without the C extensions. I tried it with a simple script and it worked (pretty slow, but it doesn?t matter). But when I add the rcov options to my Rake task, RCov is not invoke properly! Rakefile:

I know this is probably a meaningless metric, but I''m new to TDD and would like to know what to expect in terms of lines of code of tests to lines of code in a "typical" rails app. It seems like it could be as much as 5:1 or more. Perhaps its more like number of test methods : lines of code is closer to 1:1 ?

Now that I''m developing a big suite of specs, I really want to run Heckle and see how well I''ve done. Using r1359, when I run: spec spec/models/metadata_report_spec.rb --heckle MetadataReport the result is just to run the specs once and then exit, as though I hadn''t mentioned Heckle. I started looking though rspec to figure out why, but it''s late, so I should

How do I run Heckle with RSpec? I''ve tried rake spec --heckle but get no output. I''ve tried just -heckle too, as mentioned in the docs, but that isn''t accepted as a valid option and the help out is displayed. I have both the heckle and rspec-rails gems in my Gemfile, and running Rails 3, and have the latest beta version (at the time 17) installed. Thanks.

Hello everyone: I am currently assigned to test a big project which uses JRuby to build a web application. The reason of using JRuby is the web application is communicating with Java Service. I am writing test cases using Rspec and looking for a code coverage tool. Rcov is no doubt a nice code coverage tool. However, it is said that Rcov is not compatible with JRuby so far. Sigh....I can not

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] We''re getting intermittent (yes, intermittent!) segfaults from the build when running

Has the should_... syntax changed? I''m getting errors when running the following: should_render(:index) should_be_valid should_not_be_valid should_respond_to should_be should_render I thought the syntax changed to something like the following: obj.should render(:index) but this doesn''t seem to work. Scott

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, Brandon -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig

Is it a bad practice to use a subversion repository to the trunk of rspec and rspec_on_rails? Or rather, is it doomed to fail, since my gem will always be out of date? I know I can''t use spec, installed from gem,s if I have the latest revision of rspec and rspec_on_rails checked into my plugins directory. But I should still be able to use it with the --drb option, correct?