similar to: heckle and rspec on rails

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

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.

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.

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

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,

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

After a long week agonizing over a scheduling library, and then specing it out rather quickly, I''ve got some work I''m pretty happy with. As a contrast to Test::Unit, I like the way RSpec spreads my attention around the codebase while I concentrate on implementing specific behaviours. In Test::Unit, I tend to write tests around the private methods of the object under test. I

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

Anyone else having an issue with route-generation in specs breaking as of Rails trunk r6062? When I run my specs at r6061, they all pass, and in 6062 I get a trace like this every time my controller generates a route: TypeError in ''Requesting /artists/1 using PUT should redirect to the artist'' can''t convert Fixnum into String (eval):19:in `artist_url''

I spent the last couple of days getting my sea legs with Rails and RSpec. I''d been waiting til things seemed calmer before jumping in, and I''m overall very happy with my experience so far. My only real annoyance so far has been forgetting to call "do_post" or "do_create" from my specify blocks. My mocks don''t get the calls they want, and it usually

The new "pending" example feature reminds me of a feature I''ve been bouncing around in my head, to aid in refactoring. Often, when I''m changing existing behaviour, I know that certain aspects of the old behaviour should change. Imagine changing the "it" method to perhaps "not" or "old" or "removed"... The behaviour would be to

I wrote this abomination just now, and wonder if anyone else has had experience with the pattern behind it. In short, I''m specing an after_create hook on an ActiveRecord model, that calls a bunch of private methods. Instead of stubbing all those private methods (which is verboten anyway, as well as impossible because creating the object which owns those methods is what I''m

Mongrelians, I''ve just posted a GemPlugin for Mongrel, which allows you to skip all header and status-code generation, effectively hijacking the socket for whatever your needs are, from inside the depths of any Rails, Camping, Merb etc application. http://mongrel-raw-out.rubyforge.org/ or gem install mongrel_raw_output I use the plugin at work, where the client insists that testing

RSpecrs, I''ve been running into some trouble lately when passing mock objects into rich views. Either I have to obscure my specs by stubbing every method the view would call on my object, or I have to resort to trickery like stubbing ActionController#render, which is also less than ideal. The solution I''ve some up with is a variant on the :null_object option that can be passed

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/

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

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

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

I''m curious, Christian Neukirchen has released test/unit[1] that seems to mirror much of RSpec, but built on Test::Unit, so in some ways less brittle from a Rails-integration perspective, and also allowing you to mix the two together as appropriate. So, has anyone made an informed comparison? I''m new enough that I don''t really know the finer points yet. The syntax is