similar to: Promoting options to heckle?

I''ve tried running Heckle with rspec on some of my classes, but keep getting (what I believe to be) an infinite recursion. Is there some way to supply extra options to heckle via. rspec? Scott

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

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

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.

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

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''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/

The RSpec Development Team is pleased to announce the release of RSpec 0.7.5. This release adds support for Heckle - Seattle''rb''s code mutation tool. There are also several bug fixes to the RSpec core and the RSpec on Rails plugin. Changes: http://rspec.rubyforge.org/changes.html Download: http://rubyforge.org/frs/?group_id=797 or gem install rspec Happy spec''ing,

Fellow hecklers, Just spent a while getting this working. Turns out heckle will heckle a whole module and sub-modules with one call, so with a bit of string matching, you can build a nice tool to heckle your whole app and report any failures. Was going to post to the list, as the first version was about 4 lines long, but I''ve embellished it slightly (I got carried away), so

Hey all, I see examples showing up that look like this: describe Thing do before(:each) do @thing = Thing.new end it do @thing.should be_something end end This will produce output like this: Thing - should be something But "it do" is driving me mad :( We need a better word. Of course, ''specify'' has not been completely removed, so you can still do

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 ?

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

While the spirit of BDD is to spec first and code second, many of us have legacy code. Worse, some of us have legacy code without very good coverage. Recognizing that *I* have such code, I created a script that grinds through your .rb files and creates placeholder specs for each public method. While it is more sensible to spec behavior of code function than of individual methods, this

On Oct 31, 2007 11:36 AM, Scott Taylor <mailing_lists at railsnewbie.com> wrote: > When can we expect the next release of rspec? Definitely by the end of November. Likely by mid-November. Hopefully in a matter of days. The next release will be 1.1.0. We''re going to a release model in which 1.odd.x will be considered experimental. This means that while we will document

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:

Hi, Running: Ruby 1.8.7 p72, RSpec 1.1.12 and rcov 0.8.1.2.0, I get the following error message with $ rake spec:rcov -- /usr/local/ruby1.8.7//lib/ruby/1.8/rexml/formatters/pretty.rb:131:in `[]'': no implicit conversion from nil to integer (TypeError) from /usr/local/ruby1.8.7//lib/ruby/1.8/rexml/formatters/pretty.rb:131:in `wrap'' from

I saw the RCov page at http://rspec.rubyforge.org/tools/rcov.html and decided to add it to my project. My rakefile looks like this: require "rake" require "spec/rake/spectask" desc "Run all specs with RCov" Spec::Rake::SpecTask.new("spec:rcov") do |t| t.spec_files = FileList["spec/**/*_spec.rb"] t.rcov = true end When I run rake spec:rcov,

I''ve finally managed to find some time to do some serious work on Mocha. There are some code snippets on my blog (http://blog.floehopper.org/articles/2007/04/12/preview-of-latest-mocha-changes) showing the new functionality available in trunk (revision 128). I don''t don''t know how many people out there are using trunk, but it would be great to get some feedback on these

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