similar to: autometric gem

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 searching for code analysing tools for Ruby (on Rails). I know some tools for Java and DotNet but I can''t seem to find much for Ruby. Things I''m interested in are metrics like coupling (fan-in, fan-out), complexity (McCabe), inheritance nesting levels etc. The only tools I found so far are saikuro(only mccabe) and kwala (seems like a frontend for saikuro) If you

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

I just ran into this error after updating rails and the rspec_on_rails plugin (both are on edge): /Users/ben/Work/wizzdl/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:263:in `load_missing_constant'': uninitialized constant ActionView::Helpers::PaginationHelper (NameError) from /Users/ben/Work/wizzdl/vendor/rails/activerecord/

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

Is it possible to access the described class in a shared behavior? I''m trying to do something like this: describe "Siberian feline", :shared => true do described_class_instance_as :feline, :name => "fluffy", :breed => "Siberian" # or maybe before(:all) do @feline = described_class.new(:name => "fluffy", :breed =>

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 new and using Ruby on Rails 3 but when I run $ autotest nothing happens (I have growl installed). If I run $ rspec spec then I get the ''Finished in 0.07253 seconds seconds 2 example, 0 failures'' message I have the following gems installed for autotest (checked via $ gem list): autotest (4.3.2) autotest-fsevent (0.2.4, 0.2.2) autotest-growl (0.2.9, 0.2.4)

Hi all - I''ve just posted a quick plugin that adds notification of test failures via the Growl framework (http://growl.info) for OS X users. Its a great way to keep up with your test suite, especially when coupled with autotest. And if you''re anything like me, you probably already have Growl rocking. Anyway, see my blog for details on installing the plugin:

Hi all, I looked on the mailing list for metric_fu, but didn''t find it -- so at the risk of being redundant, it looks really useful. "Metric_fu is a set of rake tasks that make it easy to generate metrics reports. It uses Saikuro <http://saikuro.rubyforge.org/>, Flog<http://ruby.sadi.st/Flog.html>, Rcov <http://eigenclass.org/hiki.rb?rcov>,

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 posted a quick screencast demonstrating some BDD with RSpec yesterday: http://wincent.com/a/about/wincent/weblog/archives/2007/05/ behaviourdriven.php I''m a C/Objective-C programmer who knows a bit of Ruby, almost nothing about Rails, and in BDD I can really only claim "new but interested" status. It''s not scripted, it''s totally improvised and

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

I''m having trouble using autotest with rspec on a non-rails project. my Rspec gem is version 1.0.8, ZenTest is 3.6.2 project structure $ ls * lib: parser.rb spec: parser_spec.rb autotest finds and runs the spec, but it won''t detect changes to lib/parser.rb I know it''s something stupid, but... help? -- Rick DeNatale My blog on Ruby

On Jun 9, 2017, at 1:58 PM, Robbie van der Walle <rvanderwalle at gmail.com> wrote: > > What I wonder if the shutdown is done proper. Does the shutdown command use umount to prevent disk corruption? Yes, it prevents filesystem corruption, but I am not sure if it bothers to save the desktop state. You can check the "last" logs to see if it was cleanly shut down: $ last

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/